Apparatus, system and method of communication over common control channels

ABSTRACT

Some demonstrative embodiments include devices, systems and/or methods of communication over common control channels. For example, an apparatus may include logic and circuitry configured to cause a User Equipment (UE) to determine a selected Common Control Channel (CCCH) message configuration from a first predefined message configuration and a second predefined message configuration, the first predefined message configuration having a first predefined message bit-size, the second predefined message configuration having a second predefined message bit-size; to generate an Uplink (UL) CCCH message according to the selected CCCH message configuration, the UL CCCH message comprising a Medium Access Control (MAC) header comprising a Logical Channel Identify (ID) (LCID) field having a value corresponding to the selected CCCH message configuration; and to transmit the UL CCCH message to a Next Generation Node B (gNB) over a logical channel corresponding to the selected CCCH message configuration.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent Application No. 62/688,297 entitled “MECHANISMS FORSUPPORTING MULTIPLE COMMON CONTROL LOGICAL CHANNELS”, filed Jun. 21,2018, the entire disclosure of which is incorporated herein byreference.

TECHNICAL FIELD

Some embodiments described herein generally relate to communication overcommon control channels.

BACKGROUND

A cellular network may include a plurality of User Equipment (UEs) and aplurality of cellular nodes, e.g., base stations.

Common Control Channels may be used to transfer control informationbetween the UEs and the cellular nodes.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of an architecture of a system, inaccordance with some demonstrative embodiments.

FIG. 3 is a schematic illustration of an infrastructure equipment, inaccordance with some demonstrative embodiments.

FIG. 4 is a schematic illustration of a platform, in accordance withsome demonstrative embodiments.

FIG. 5 is a schematic illustration of a baseband and Radio Frequency(RF) configuration, in accordance with some demonstrative embodiments.

FIG. 6 is a schematic illustration of interfaces of a basebandcircuitry, in accordance with some demonstrative embodiments.

FIG. 7 is a schematic flow-chart illustration of a method ofcommunication over common control channels, in accordance with somedemonstrative embodiments.

FIG. 8 is a schematic flow-chart illustration of a method ofcommunication over common control channels, in accordance with somedemonstrative embodiments.

FIG. 9 is a schematic illustration of a product, in accordance with somedemonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment,” “an embodiment,” “demonstrativeembodiment,” “various embodiments,” etc., indicate that theembodiment(s) so described may include a particular feature, structure,or characteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a User Equipment (UE), a Mobile Device (MD), awireless station (STA), a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a sensor device, anInternet of Things (IoT) device, a wearable device, a handheld device, aPersonal Digital Assistant (PDA) device, a handheld PDA device, anon-board device, an off-board device, a hybrid device, a vehiculardevice, a non-vehicular device, a mobile or portable device, a consumerdevice, a non-mobile or non-portable device, a wireless communicationstation, a wireless communication device, a wireless Access Point (AP),a wired or wireless router, a wired or wireless modem, a video device,an audio device, an audio-video (A/V) device, a wired or wirelessnetwork, a wireless area network, a Wireless Video Area Network (WVAN),a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal AreaNetwork (PAN), a Wireless PAN (WPAN), and the like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing 3rd Generation Partnership Project(3GPP) and/or Long Term Evolution (LTE) specifications (including 3GPPTS 38.331 (“3GPP TS 38.331 V15.2.1 (2018-06); Technical Specification;3rd Generation Partnership Project; Technical Specification Group RadioAccess Network; NR; Radio Resource Control (RRC) protocol specification(Release 15)); and/or 3GPP TS 38.321 (“3GPP TS 38.321 V15.2.0 (2018-06);Technical Specification; 3rd Generation Partnership Project; TechnicalSpecification Group Radio Access Network; NR; Medium Access Control(MAC) protocol specification (Release 15)”)) and/or future versionsand/or derivatives thereof, devices and/or networks operating inaccordance with existing IEEE 802.11 standards (including IEEE802.11-2016 (IEEE 802.11-2016, IEEE Standard for Informationtechnology—Telecommunications and information exchange between systemsLocal and metropolitan area networks—Specific requirements Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications, Dec. 7, 2016), and/or future versions and/or derivativesthereof, units and/or devices which are part of the above networks, andthe like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Frequency-Division Multiplexing (FDM), Orthogonal FDM(OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA),Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA),Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extendedGPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation(MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System(GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBee™, Ultra-Wideband (UWB),Global System for Mobile communication (GSM), second generation (2G),2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, LongTerm Evolution (LTE) cellular system, LTE advance cellular system,High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink PacketAccess (HSUPA), High-Speed Packet Access (HSPA), HSPA+, Single CarrierRadio Transmission Technology (1XRTT), Evolution-Data Optimized (EV-DO),Enhanced Data rates for GSM Evolution (EDGE), and the like. Otherembodiments may be used in various other devices, systems and/ornetworks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a communicationsignal includes transmitting the communication signal and/or receivingthe communication signal. For example, a communication unit, which iscapable of communicating a communication signal, may include atransmitter to transmit the communication signal to at least one othercommunication unit, and/or a communication receiver to receive thecommunication signal from at least one other communication unit. Theverb communicating may be used to refer to the action of transmitting orthe action of receiving. In one example, the phrase “communicating asignal” may refer to the action of transmitting the signal by a firstdevice, and may not necessarily include the action of receiving thesignal by a second device. In another example, the phrase “communicatinga signal” may refer to the action of receiving the signal by a firstdevice, and may not necessarily include the action of transmitting thesignal by a second device. The communication signal may be transmittedand/or received, for example, in the form of Radio Frequency (RF)communication signals, and/or any other type of signal.

As used herein, the term “circuitry” may refer to, be part of, orinclude, an Application Specific Integrated Circuit (ASIC), anintegrated circuit, an electronic circuit, a processor (shared,dedicated, or group), and/or memory (shared, dedicated, or group), thatexecute one or more software or firmware programs, a combinational logiccircuit, and/or other suitable hardware components that provide thedescribed functionality. In some embodiments, the circuitry may beimplemented in, or functions associated with the circuitry may beimplemented by, one or more software or firmware modules. In someembodiments, circuitry may include logic, at least partially operable inhardware.

The term “logic” may refer, for example, to computing logic embedded incircuitry of a computing apparatus and/or computing logic stored in amemory of a computing apparatus. For example, the logic may beaccessible by a processor of the computing apparatus to execute thecomputing logic to perform computing functions and/or operations. In oneexample, logic may be embedded in various types of memory and/orfirmware, e.g., silicon blocks of various chips and/or processors. Logicmay be included in, and/or implemented as part of, various circuitry,e.g. radio circuitry, receiver circuitry, control circuitry, transmittercircuitry, transceiver circuitry, processor circuitry, and/or the like.In one example, logic may be embedded in volatile memory and/ornon-volatile memory, including random access memory, read only memory,programmable memory, magnetic memory, flash memory, persistent memory,and the like. Logic may be executed by one or more processors usingmemory, e.g., registers, stuck, buffers, and/or the like, coupled to theone or more processors, e.g., as necessary to execute the logic.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a set of switched beam antennas, and/or thelike.

The term “cell”, as used herein, may include a combination of networkresources, for example, downlink and optionally uplink resources. Theresources may be controlled and/or allocated, for example, by a node(also referred to as a “base station”), or the like. The linking betweena carrier frequency of the downlink resources and a carrier frequency ofthe uplink resources may be indicated in system information transmittedon the downlink resources.

Some demonstrative embodiments are described herein with respect to anLTE network, a Fifth Generation (5G) network, or a New Radio (NR)network. However, other embodiments may be implemented in any othersuitable cellular network or system, for example, future 3GPP systems,e.g., Sixth Generation (6G)) systems, and the like.

Other embodiments may be used in conjunction with any other suitablewireless communication network.

Reference is now made to FIG. 1 , which schematically illustrates ablock diagram of a system 100, in accordance with some demonstrativeembodiments.

As shown in FIG. 1 , in some demonstrative embodiments, system 100 mayinclude one or more wireless communication devices capable ofcommunicating content, data, information and/or signals via one or morewireless mediums (WM). For example, system 100 may include at least oneUser Equipment (UE) 102, capable of communicating with one or morewireless communication networks and/or one or more cellular networks,e.g., as described below.

In one example, the term “user equipment” or “UE”, as used herein, mayinclude a device with radio communication capabilities, and/or maydescribe a remote user of network resources in a communications network.The term “user equipment” or “UE”, as used herein, may include a client,a mobile, a mobile device, a mobile terminal, a user terminal, a mobileunit, a mobile station, a mobile user, a subscriber, a user, a remotestation, an access agent, a user agent, a receiver, a radio equipment, areconfigurable radio equipment, a reconfigurable mobile device, and/orthe like.

In some demonstrative embodiments, UE 102 may include, for example, aMobile Device (MD), a Station (STA), a mobile computer, a laptopcomputer, a notebook computer, a tablet computer, an Ultrabook™computer, an Internet of Things (IoT) device, a wearable device, asensor device, a mobile internet device, a handheld computer, a handhelddevice, a storage device, a PDA device, a handheld PDA device, anon-board device, an off-board device, a hybrid device (e.g., combiningcellular phone functionalities with PDA device functionalities), aconsumer device, a vehicular device, a non-vehicular device, a mobile orportable device, a mobile phone, a cellular telephone, a PCS device, amobile or portable GPS device, a DVB device, a relatively smallcomputing device, a non-desktop computer, a “Carry Small Live Large”(CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC),a Mobile Internet Device (MID), an “Origami” device or computing device,a video device, an audio device, an A/V device, a gaming device, a mediaplayer, a Smartphone, e.g., handheld touchscreen mobile computingdevices connectable to one or more cellular networks, or the like.

In one example, the term “user equipment” or “UE”, as used herein, mayinclude any type of wireless and/or wired device or any computing deviceincluding a wireless communications interface.

In some demonstrative embodiments, UE 102 may include a mobile or anon-mobile computing device, for example, consumer electronics devices,cellular phones, smartphones, feature phones, tablet computers, wearablecomputer devices, personal digital assistants (PDAs), pagers, wirelesshandsets, desktop computers, laptop computers, in-vehicle infotainment(IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC),head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtopmobile equipment (DME), mobile data terminals (MDTs), Electronic EngineManagement System (EEMS), electronic/engine control units (ECUs),Electronic/Engine Control Modules (ECMs), embedded systems,microcontrollers, control modules, engine management systems (EMS),networked or “smart” appliances, Machine-Type Communications (MTC)devices, Machine-To-Machine (M2M), Internet of Things (IoT) devices,and/or the like.

In some embodiments, UE 102 may include an IoT UE, which may include anetwork access layer designed for low-power IoT applications utilizingshort-lived UE connections. An IoT UE may utilize technologies such asM2M or MTC for exchanging data with an MTC server or device, forexample, via a Public Land Mobile Network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, and/or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data.

In one example, an IoT network may describe interconnecting IoT UEs,which may include uniquely identifiable embedded computing devices,e.g., within an Internet infrastructure, with short-lived connections.For example, the IoT UEs may execute background applications, e.g.,keep-alive messages, status updates, and the like, to facilitateconnections of the IoT network.

In some demonstrative embodiments, system 100 may include an AccessNetwork (AN), for example, a Radio Access Network (RAN) 110, e.g., asdescribed below.

In some demonstrative embodiments, RAN 110 may include for example, anEvolved Universal Mobile Telecommunications System (UMTS) TerrestrialRadio Access Network (E-UTRAN), an NG RAN or a 5G RAN, for example, inaccordance with 3GPP Technical Specifications (TS).

In other embodiments, RAN 110 may include any other RAN, e.g., a legacyRAN, for example, a UMTS Terrestrial Radio Access Network (UTRAN) orGlobal System for Mobile Communications or Groupe Special Mobile (GSM)EDGE (GSM Evolution) Radio Access Network (GERAN).

In one example, the term “NG RAN”, as used herein, may include a RANthat operates in an NR or 5G system, and/or the term “E-UTRAN”, as usedherein, may include a RAN that operates in an LTE or a 4G system.

In some demonstrative embodiments, UE 102 may communicate with RAN 110,for example, via one or more channels or connections 104, e.g., asdescribed below.

In some demonstrative embodiments, channels 104 may include a physicalcommunications interface or layer, e.g., as described below.

In one example, the term “channel”, as used herein, may include anytransmission medium, either tangible or intangible, which is used tocommunicate data or a data stream. The term “channel” may be synonymouswith and/or equivalent to “communications channel,” “data communicationschannel,” “transmission channel,” “data transmission channel,” “accesschannel,” “data access channel,” “link,” “data link,” “carrier,”“radiofrequency carrier,” and/or any other like term denoting a pathwayor medium through which data is communicated. Additionally oralternatively, the term “link”, as used herein, may refer to aconnection between two devices through a Radio Access Technology (RAT)for a purpose of transmitting and/or receiving information.

In some demonstrative embodiments, channels 104 may include an airinterface to enable communicative coupling, for example, in accordancewith 3GPP Specifications. For example, channels 104 may be configured inaccordance with cellular communications protocols, e.g., a Global Systemfor Mobile Communications (GSM) protocol, a Code-Division MultipleAccess (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTTover Cellular (POC) protocol, a Universal Mobile TelecommunicationsSystem (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, afifth generation (5G) protocol, a New Radio (NR) protocol, and/or any ofthe other communications protocols discussed herein.

In some demonstrative embodiments, RAN 110 may include at least onenode, e.g., a base station (BS), for example, to manage communication ofRAN 110 and/or to enable connections or channels 104, e.g., as describedbelow.

In some demonstrative embodiments, the node may include, may operate as,and/or may perform the functionality of, a next Generation Node B (gNB)140, e.g., as described below.

In other embodiments, the node may include a Base Station (BS), RANnodes, evolved NodeBs (eNBs), NodeBs, Road Side Units (RSUs),Transmission Reception Points (TRxPs or TRPs), and the like. Forexample, the node may include ground stations, e.g., terrestrial accesspoints, or satellite stations, providing coverage within a geographicarea, e.g., a cell.

In one example, the term “Road Side Unit” or “RSU”, as used herein, mayrefer to any transportation infrastructure entity implemented in or by agNB/eNB/RAN node or a stationary. An RSU implemented in or by a UE maybe referred to as a “UE-type RSU”, an RSU implemented in or by an eNBmay be referred to as an “eNB-type RSU.”

In one example, the term “NG RAN node”, as used herein, may refer to aRAN node that operates in an NR or 5G system, e.g., a gNB, and/or theterm “E-UTRAN node”, as used herein, may refer to a RAN node thatoperates in an LTE or 4G system, e.g., an eNB.

In some demonstrative embodiments, gNB 140 may be implemented as one ormore of a dedicated physical device such as a macrocell base station,and/or a Low Power (LP) base station for providing femtocells, picocellsor other like cells having smaller coverage areas, smaller usercapacity, and/or higher bandwidth, e.g., compared to macrocells.

In other embodiments, gNB 140 may be implemented as one or more softwareentities running on server computers as part of a virtual network, whichmay be referred to as a Cloud Radio Access Network (CRAN).

In other embodiments, gNB 140 may represent individual gNB-DistributedUnits (DUs) that are connected to a gNB-Centralized Unit (CU), e.g., viaan F1 interface.

In some demonstrative embodiments, gNB 140 may be configured toterminate an air interface protocol and/or may be the first point ofcontact for the UE 102.

In some demonstrative embodiments, gNB 140 may be configured to performvarious logical functions for the RAN 110 including, for example, RadioNetwork Controller (RNC) functions, e.g., radio bearer management,uplink and downlink dynamic radio resource management and data packetscheduling, mobility management, and/or any other additional oralternative functionalities.

In other embodiments, gNB 140 may include any other functionality and/ormay perform the functionality of any other cellular node, networkcontroller, base station, or any other node or network device.

In some demonstrative embodiments, elements of system 100 may be capableof communicating over one or more wireless mediums, for example, a radiochannel, a cellular channel, an RF channel, a WiFi channel, an IRchannel, and the like. One or more elements of system 100 may optionallybe capable of communicating over any suitable wired communication links.

In some demonstrative embodiments, UE 102 and/or gNB 140 may include oneor more communication interfaces to perform communication between UE102, gNB 140, and/or with one or more other wireless communicationdevices, e.g., as described below.

In some demonstrative embodiments, gNB 140 may include an air interface,for example, a radio 144, including circuitry and/or logic configured tocommunicate with UE 102 via the channels 104.

In some demonstrative embodiments, UE 102 may include an air interface,for example, a radio 114, including circuitry and/or logic configured tocommunicate with RAN 110, for example, via a node, e.g., gNB 140, viathe channels 104.

In some demonstrative embodiments, radio 114 and/or radio 144 mayinclude one or more wireless receivers (Rx) including circuitry and/orlogic to receive wireless communication signals, RF signals, frames,blocks, transmission streams, packets, messages, data items, and/ordata. For example, radio 114 may include at least one receiver 116,and/or radio 144 may include at least one receiver 146.

In some demonstrative embodiments, radio 114 and/or radio 144 mayinclude one or more wireless transmitters (Tx) including circuitryand/or logic to transmit wireless communication signals, RF signals,frames, blocks, transmission streams, packets, messages, data items,and/or data. For example, radio 114 may include at least one transmitter118, and/or radio 144 may include at least one transmitter 148.

In some demonstrative embodiments, radio 114, radio 144, transmitter118, transmitter 148, receiver 116, and/or receiver 146 may includecircuitry; logic; Radio Frequency (RF) elements, circuitry and/or logic;baseband elements, circuitry and/or logic; modulation elements,circuitry and/or logic; demodulation elements, circuitry and/or logic;amplifiers; analog to digital and/or digital to analog converters;filters; and/or the like.

In some demonstrative embodiments, radio 114 and/or radio 144 mayinclude, or may be associated with, one or more antennas. For example,radio 114 may include, or may be associated with, one or more antennas107; and/or radio 144 may include, or may be associated with, one ormore antennas 147.

In one example, UE 102 may include a single antenna 107. In anotherexample, UE 102 may include two or more antennas 107.

In one example, gNB 140 may include a single antenna 147. In anotherexample, gNB 140 may include two or more antennas 147.

Antennas 107 and/or 147 may include any type of antennas suitable fortransmitting and/or receiving wireless communication signals, blocks,frames, transmission streams, packets, messages and/or data. Forexample, antennas 107 and/or 147 may include any suitable configuration,structure and/or arrangement of one or more antenna elements,components, units, assemblies and/or arrays. In some embodiments,antennas 107 and/or 147 may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, antennas 107 and/or 147 may implement transmit andreceive functionalities using common and/or integrated transmit/receiveelements.

In some demonstrative embodiments, UE 102 may include a controller 124,and/or gNB 140 may include a controller 154. Controller 124 may beconfigured to perform and/or to trigger, cause, instruct and/or controlUE 102 to perform, one or more communications, to generate and/orcommunicate one or more messages and/or transmissions, and/or to performone or more functionalities, operations and/or procedures between UE 102and gNB 140, and/or one or more other devices; and/or controller 154 maybe configured to perform, and/or to trigger, cause, instruct and/orcontrol gNB 140 to perform, one or more communications, to generateand/or communicate one or more messages and/or transmissions, and/or toperform one or more functionalities, operations and/or proceduresbetween UE 102 and gNB 140, and/or one or more other devices, e.g., asdescribed below.

In some demonstrative embodiments, controllers 124 and/or 154 mayinclude, or may be implemented, partially or entirely, by circuitryand/or logic, e.g., one or more processors including circuitry and/orlogic, memory circuitry and/or logic, Media-Access Control (MAC)circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic,baseband (BB) circuitry and/or logic, a BB processor, a BB memory,Application Processor (AP) circuitry and/or logic, an AP processor, anAP memory, and/or any other circuitry and/or logic, configured toperform the functionality of controllers 124 and/or 154, respectively.Additionally or alternatively, one or more functionalities ofcontrollers 124 and/or 154 may be implemented by logic, which may beexecuted by a machine and/or one or more processors, e.g., as describedbelow.

In one example, controller 124 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause, trigger and/or control a device, e.g., UE 102, to perform one ormore operations, communications and/or functionalities, e.g., asdescribed herein. In one example, controller 124 may include at leastone memory, e.g., coupled to the one or more processors, which may beconfigured, for example, to store, e.g., at least temporarily, at leastsome of the information processed by the one or more processors and/orcircuitry, and/or which may be configured to store logic to be utilizedby the processors and/or circuitry.

In one example, controller 154 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause, trigger and/or control a device, e.g., gNB 140, to perform one ormore operations, communications and/or functionalities, e.g., asdescribed herein. In one example, controller 154 may include at leastone memory, e.g., coupled to the one or more processors, which may beconfigured, for example, to store, e.g., at least temporarily, at leastsome of the information processed by the one or more processors and/orcircuitry, and/or which may be configured to store logic to be utilizedby the processors and/or circuitry.

In some demonstrative embodiments, UE 102 may include a messageprocessor 128 configured to generate, process and/or access one ormessages communicated by UE 102.

In one example, message processor 128 may be configured to generate oneor more messages to be transmitted by UE 102, and/or message processor128 may be configured to access and/or to process one or more messagesreceived by UE 102, e.g., as described below.

In one example, message processor 128 may include at least one firstcomponent configured to generate a message, for example, in the form ofa frame, field, information element and/or protocol data unit, forexample, a MAC Protocol Data Unit (MPDU); at least one second componentconfigured to convert the message into a PHY Protocol Data Unit (PPDU),for example, by processing the message generated by the at least onefirst component, e.g., by encoding the message, modulating the messageand/or performing any other additional or alternative processing of themessage; and/or at least one third component configured to causetransmission of the message over a communication medium, e.g., over awireless communication channel in a wireless communication frequencyband, for example, by applying to one or more fields of the PPDU one ormore transmit waveforms. In other embodiments, message processor 128 maybe configured to perform any other additional or alternativefunctionality and/or may include any other additional or alternativecomponents to generate and/or process a message to be transmitted.

In some demonstrative embodiments, gNB 140 may include a messageprocessor 158 configured to generate, process and/or access one ormessages communicated by gNB 140.

In one example, message processor 158 may be configured to generate oneor more messages to be transmitted by gNB 140, and/or message processor158 may be configured to access and/or to process one or more messagesreceived by gNB 140, e.g., as described below.

In one example, message processor 158 may include at least one firstcomponent configured to generate a message, for example, in the form ofa frame, field, information element and/or protocol data unit, forexample, a MAC Protocol Data Unit (MPDU); at least one second componentconfigured to convert the message into a PHY Protocol Data Unit (PPDU),for example, by processing the message generated by the at least onefirst component, e.g., by encoding the message, modulating the messageand/or performing any other additional or alternative processing of themessage; and/or at least one third component configured to causetransmission of the message over a communication medium, e.g., over awireless communication channel in a wireless communication frequencyband, for example, by applying to one or more fields of the PPDU one ormore transmit waveforms. In other embodiments, message processor 158 maybe configured to perform any other additional or alternativefunctionality and/or may include any other additional or alternativecomponents to generate and/or process a message to be transmitted.

In some demonstrative embodiments, message processors 128 and/or 158 mayinclude circuitry and/or logic, e.g., processor circuitry and/or logic,memory circuitry and/or logic, Media-Access Control (MAC) circuitryand/or logic, Physical Layer (PHY) circuitry and/or logic, and/or anyother circuitry and/or logic, configured to perform the functionality ofmessage processors 128 and/or 158. Additionally or alternatively, one ormore functionalities of message processors 128 and/or 158 may beimplemented by logic, which may be executed by a machine and/or one ormore processors, e.g., as described below.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of controller 124,and/or at least part of the functionality of message processor 158 maybe implemented as part of controller 154.

In other embodiments, the functionality of message processor 128 may beimplemented as part of any other element of UE 102, and/or thefunctionality of message processor 158 may be implemented as part of anyother element of gNB 140.

In some demonstrative embodiments, at least part of the functionality ofcontroller 124 and/or message processor 128 may be implemented by anintegrated circuit, for example, a chip, e.g., a System on Chip (SoC).In one example, the chip or SoC may be configured to perform one or morefunctionalities of radio 114. For example, the chip or SoC may includeone or more elements of controller 124, one or more elements of messageprocessor 128, and/or one or more elements of radio 114. In one example,controller 124, message processor 128, and radio 114 may be implementedas part of the chip or SoC.

In other embodiments, controller 124, message processor 128 and/or radio114 may be implemented by one or more additional or alternative elementsof UE 102.

In some demonstrative embodiments, at least part of the functionality ofcontroller 154 and/or message processor 158 may be implemented by anintegrated circuit, for example, a chip, e.g., a System on Chip (SoC).In one example, the chip or SoC may be configured to perform one or morefunctionalities of radio 144. For example, the chip or SoC may includeone or more elements of controller 154, one or more elements of messageprocessor 158, and/or one or more elements of radio 144. In one example,controller 154, message processor 158, and radio 144 may be implementedas part of the chip or SoC.

In other embodiments, controller 154, message processor 158 and/or radio144 may be implemented by one or more additional or alternative elementsof gNB 140.

In some demonstrative embodiments, UE 102 may include, for example, oneor more of a processor 191, an input unit 192, an output unit 193, amemory unit 194, and/or a storage unit 195; and/or gNB 140 may include,for example, one or more of a processor 181, an input unit 182, anoutput unit 183, a memory unit 184, and/or a storage unit 185. Devices102 and/or 140 may optionally include other suitable hardware componentsand/or software components. In some demonstrative embodiments, some orall of the components of UE 102 and/or gNB 140 may be enclosed in acommon housing or packaging, and may be interconnected or operablyassociated using one or more wired or wireless links. In otherembodiments, components of UE 102 and/or gNB 140 may be distributedamong multiple or separate devices.

In some demonstrative embodiments, processor 191 and/or processor 181may include, for example, a Central Processing Unit (CPU), a DigitalSignal Processor (DSP), one or more processor cores, a single-coreprocessor, a dual-core processor, a multiple-core processor, amicroprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 191 executes instructions,for example, of an Operating System (OS) of UE 102 and/or of one or moresuitable applications. Processor 181 may execute instructions, forexample, of an Operating System (OS) of gNB 140 and/or of one or moresuitable applications.

In some demonstrative embodiments, input unit 192 and/or input unit 182may include, for example, a keyboard, a keypad, a mouse, a touch-screen,a touch-pad, a track-ball, a stylus, a microphone, or other suitablepointing device or input device. Output unit 193 and/or output unit 183includes, for example, a monitor, a screen, a touch-screen, a flat paneldisplay, a Light Emitting Diode (LED) display unit, a Liquid CrystalDisplay (LCD) display unit, a plasma display unit, one or more audiospeakers or earphones, or other suitable output devices.

In some demonstrative embodiments, memory unit 194 and/or memory unit184 includes, for example, a Random Access Memory (RAM), a Read OnlyMemory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flashmemory, a volatile memory, a non-volatile memory, a cache memory, abuffer, a short term memory unit, a long term memory unit, or othersuitable memory units. Storage unit 195 and/or storage unit 185includes, for example, a hard disk drive, a floppy disk drive, a CompactDisk (CD) drive, a CD-ROM drive, a DVD drive, or other suitableremovable or non-removable storage units. Memory unit 194 and/or storageunit 195, for example, may store data processed by UE 102. Memory unit184 and/or storage unit 185, for example, may store data processed bygNB 140.

In some demonstrative embodiments, UE 102 and gNB 140 may communicateover a one or more Common Control Channel (CCCH) messages, for example,over one or more CCCH logical channels, e.g., as described below.

In some demonstrative embodiments, an NR radio interface, e.g., radio114 and/or radio 144, may be configured to support a small CCCH messageof 48 bits, e.g., in a worst case scenario, and/or to support a largeCCCH message of more than 64 bits, e.g., in other cases.

In some demonstrative embodiments, a transport block size may be used,for example, to determine a CCCH message size, e.g., for LTE. However,this approach may not be defined for NR. For example, the transportblock size may not be used in NR, and a specific logical channel ID(LCID) value may indicate 48 bit. Therefore, there may be a need todefine a solution for NR, for example, for a 64-bit CCCH message.

In one example, using an extra bit in a 64-bit CCCH message, e.g., toindicate the 64 bit CCCH message, for example, in compliance with LTE,may be inefficient, e.g., may be size constraining.

In one example, a CCCH message without a length field, and with a newLCID may be supported. For example, a payload length corresponding tothe new LCID may be fixed to a size of 48 bits, e.g., as follows:

TABLE 1 Index LCID value 100001 CCCH of size 48 bits

In some demonstrative embodiments, there may be a need to support atleast two different CCCH sizes, e.g., including CCCH sizes of 48 bitsand 64 bits, for example, to fit Transport Block (TB) sizescorresponding to payloads of 56 bits and 72 bits, e.g., including a MACheader. In other embodiments, any other additional or alternative CCCHmessage sizes may be implemented.

In some demonstrative embodiments, 64-bit CCCH message configurationsand/or indications may be defined, e.g., as described below.

For example, a user plane may support a new LCID for a fixed CCCHmessage of 48 bits. For example, a CCCH LCID may be used with atwo-octet MAC header including a length field. According to thisexample, neither of the LCIDs can be used for a CCCH message of 64 bits,e.g., when the TB can only support 72 data bits.

Some demonstrative embodiments may be implemented to define anadditional LCID, for example, for a fixed 64 bit CCCH message.

In some demonstrative embodiments, the user plane may be changed to usea second CCCH LCID, for example, when a message (msg3) does not containany other MAC Control Element (CE).

In some demonstrative embodiments, a new LCID may be used for a 64 bitCCCH message, e.g., an LCID different from the LCID for 48 bit CCCHmessages, e.g., as described below.

In some demonstrative embodiments, a new logical CCCH channel (CCCH1)may be defined, for example, to correspond to the new LCID, e.g., asdescribed below.

In some demonstrative embodiments, a new set of one or more CCCHmessages may be defined to communicate on the logical CCCH1 channeland/or to use the new LCID, e.g., as described below.

In some demonstrative embodiments, larger CCCH messages, e.g., 64-bitCCCH messages, may be associated, e.g., only associated, with the newCCCH, e.g., the CCCH1, and/or may use the new LCID, e.g., as describedbelow.

In some demonstrative embodiments, using the new LCID and/or the newCCCH channel may provide forward compatibility, for example, forextensions in the future, and/or may free up one bit in a CCCH messageof a smaller size, e.g., the 48-bit CCCH message.

Some demonstrative embodiments may be implemented to provide acapability to define larger versions, e.g., even for all other CCCHmessages, and/or new CCCH messages.

Some demonstrative embodiments may be implemented to define a new LCID,e.g., an additional LCID, for example, for fixed 64 bit CCCH messages,e.g., as described below.

In some demonstrative embodiments, the new LCID may be used to indicateany suitable 64 bit CCCH messages, e.g., of one or more types asdescribed below. For example, one or more CCCH messages, e.g., even allCCCH messages, may benefit from using 64 bit CCCH messages, for example,to carry additional information and/or to have spare values for laterreleases.

In some demonstrative embodiments, a new CCCH logical channel, e.g.,CCCH1, for 64 bit messages may be defined, e.g., as described below.

In some demonstrative embodiments, 64 bit versions of one or more othermessages may be defined in the future.

Some demonstrative embodiments may be implemented to define a CCCH,e.g., CCCH1, for 64 bit CCCH messages, e.g., different from a CCCH for48 bit CCCH messages, e.g., as described below.

In some demonstrative embodiments, the CCCH for 64 bit CCCH messages,e.g., CCCH1, may be used, for example, to support even all 64 bitmessages. Hence, it may not be necessary to use a previously agreedconstruct to define a choice of Radio Network Temporary Identity(I-RNTI) lengths for a same Resume request message, e.g., as describedbelow.

Some demonstrative embodiments may be implemented to define any otheradditional or alternative CCCH messages, for example, other 64 bit CCCHmessages and/or any other CCCH messages of any other predefined size,e.g., to communicate over any other CCCH logical channel, e.g., asdescribed below.

In some demonstrative embodiments, UE 102 may be configured determine aselected CCCH message configuration, e.g., for a CCCH message, e.g., asdescribed below.

In some demonstrative embodiments, gNB 140 may be configured to indicateto UE 102 on the selected CCCH message configuration, e.g., as describedbelow.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 to determine a selected CommonControl Channel (CCCH) message configuration from a first predefinedmessage configuration and a second predefined message configuration,e.g., as described below.

In some demonstrative embodiments, the first predefined messageconfiguration may have a first predefined message bit-size, and/or thesecond predefined message configuration may have a second predefinedmessage bit-size, e.g., as described below.

In some demonstrative embodiments, the first predefined message bit-sizemay include a 48-bit size, and/or the second predefined message bit-sizemay include a 64-bit size, e.g., as described below.

In other embodiments, the first predefined message bit-size may includeany other bit size, and/or the second predefined message bit-size mayinclude any other bit size, for example, different from the firstpredefined message bit-size.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 and/or message processor 128 togenerate an Uplink (UL) CCCH message according to the selected CCCHmessage configuration, e.g., as described below.

In some demonstrative embodiments, the UL CCCH message may include aMedium Access Control (MAC) header including a Logical Channel Identify(ID) (LCID) field having a value corresponding to the selected CCCHmessage configuration, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 and/or radio 114 to transmit the ULCCCH message to gNB 140 over a logical channel corresponding to theselected CCCH message configuration, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 to determine the selected CCCHmessage configuration, for example, based on an indication in a messagefrom the gNB 140.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 to determine the selected CCCHmessage configuration, for example, based on an indication in abroadcast message from the gNB 140.

In some demonstrative embodiments, gNB 140 may broadcast or transmit theindication of the selected CCCH message configuration, e.g., asdescribed below.

In some demonstrative embodiments, controller 154 may be configured tocontrol, cause and/or trigger gNB 140 and/or radio 144 to transmit themessage including the indication of the selected CCCH messageconfiguration from the first predefined message configuration having thefirst predefined message bit-size and the second predefined messageconfiguration having the second predefined message bit-size, e.g., asdescribed below.

In some demonstrative embodiments, controller 154 may be configured tocontrol, cause and/or trigger gNB 140 and/or radio 144 to broadcast themessage, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocontrol, cause and/or trigger gNB 140 and/or radio 144 to receive the ULCCCH message from UE 102 over the logical channel corresponding to theselected CCCH message configuration. For example, the UL CCCH messagemay include the MAC header including the LCID field having the valuecorresponding to the selected CCCH message configuration, e.g., asdescribed below.

In some demonstrative embodiments, the UL CCCH message may include aRadio Resource Control (RRC) message, e.g., as described below.

In some demonstrative embodiments, the first predefined messageconfiguration may correspond to a first CCCH message type, and/or thesecond predefined message configuration may correspond to a second CCCHmessage type, for example, different from the first CCCH message type,e.g., as described below.

In some demonstrative embodiments, the first predefined messageconfiguration may include a first identifier field having a firstpredefined bit-size, and/or the second predefined message configurationmay include a second identifier field having a second predefinedbit-size, for example, different from the first predefined bit-size,e.g., as described below.

In some demonstrative embodiments, the LCID field may include a firstpredefined LCID value, or a second predefined LCID value, for example,based on the selected CCCH message configuration, e.g., as describedbelow.

In some demonstrative embodiments, the LCID field may include a firstpredefined LCID value, for example, when the selected CCCH messageconfiguration includes the first predefined message configuration, andthe LCID field may include a second predefined LCID value, differentfrom the first predefined LCID value, when the selected CCCH messageconfiguration includes the second predefined message configuration,e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 to set the LCID field to the firstpredefined LCID value, for example, when the selected CCCH messageconfiguration includes the first predefined message configuration, e.g.,as described below.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 to set the LCID field to the secondpredefined LCID value, different from the first predefined LCID value,for example, when the selected CCCH message configuration includes thesecond predefined message configuration, e.g., as described below.

In some demonstrative embodiments, a new, e.g., an additional, LCIDvalue may be defined, for example, for a fixed 64 bit CCCH message.According to this example, if the new LCID is used for 64 bit CCCHmessages, then it may be used for any 64 bit CCCH messages. For example,CCCH messages may benefit, for example, from using 64 bit CCCH messages,e.g., to carry additional information and/or from having spare valuesfor later releases.

In some demonstrative embodiments, one or more LCID values may bedefined, for example, for a MAC layer, e.g., as follows:

TABLE 2 Index LCID value 000000 CCCH of size other than 48 bits000001-100000 Identity of the logical channel 100001 CCCH of size 48bits 100010 CCCH1 of size 64 bits 100011-110101 Reserved 110110 MultipleEntry PHR (four octet Ci) 110111 Configured Grant Confirmation 111000Multiple Entry PHR (one octet Ci) 111001 Single Entry PHR 111010 C-RNTI111011 Short Truncated BSR 111100 Long Truncated BSR 111101 Short BSR111110 Long BSR 111111 Padding

For example, according to Table 2, a first LCID value, e.g., a value of“100001”, may be defined to indicate a 48-bit CCCH messageconfiguration; and/or a second LCID value, e.g., a value of “100010”,may be defined to indicate a 64-bit CCCH message configuration.

In other embodiments, any other LCID values may be defined for 48-bitCCCH message configuration, the 64-bit CCCH message configuration,and/or any other additional or alternative CCCH message configuration ofany other predefined message size.

In some demonstrative embodiments, UE 102 may set the LCID fieldaccording to Table 2m for example, to a value of “100001”, for example,when the selected CCCH message configuration includes the CCCH of size48 bits.

In some demonstrative embodiments, UE 102 may set the LCID fieldaccording to Table, 2, for example, to a value of “100010”, for example,when the selected CCCH message configuration includes the CCCH1 of size64 bits.

In some demonstrative embodiments, a first predefined messageconfiguration, e.g., the 48-bit CCCH message configuration, maycorrespond to a first logical channel, and/or a second predefinedmessage configuration, e.g., the 64-bit CCCH message configuration, maycorrespond to a second logical channel, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 to transmit the UL CCCH messageover a first logical channel (CCCH channel), for example, when theselected CCCH message configuration includes the first predefinedmessage configuration, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocontrol, cause and/or trigger UE 102 to transmit the UL CCCH messageover a second logical channel (CCCH1 channel), for example, when theselected CCCH message configuration includes the second predefinedmessage configuration, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocontrol, cause and/or trigger gNB 140 and/or radio 144 to receive the ULCCCH message over the first logical channel (CCCH channel), for example,when the selected CCCH message configuration includes the firstpredefined message configuration, e.g., as described below.

In some demonstrative embodiments, controller 154 may be configured tocontrol, cause and/or trigger gNB 140 and/or radio 144 to receive the ULCCCH message over the second logical channel (CCCH1 channel), forexample, when the selected CCCH message configuration includes thesecond predefined message configuration, e.g., as described below.

In some demonstrative embodiments, a plurality of message formats may bedefined as variations of a CCCH message, for example, a Radio ResourceControl (RRC) message, e.g., as described below.

In some demonstrative embodiments, for example, at least first andsecond message formats may be defined for an RRC message. For example,the first and second message formats may have first and secondrespective different CCCH sizes, e.g., as described below.

In some demonstrative embodiments, the first and second message formatsmay be configured to carry different information and/or informationfields of different lengths, e.g., as described below.

In some demonstrative embodiments, for example, a first message formatmay have a first CCCH size and may include a field having a first fieldsize configured to carry a truncated version of particular information;and a second message format may have a second CCCH size, e.g., longerthan the first CCCH size, and may include a field having a second fieldsize, e.g., longer than the first field size, which may be configured tocarry a longer version, e.g., even a full version, of particularinformation.

In some demonstrative embodiments, the UL CCCH message may include a RRCResume Request message, e.g., as described below.

In one example, the RRCResumeRequest message may be used to request aresumption of a suspended RRC connection and/or to perform an RAN-levelNotification Areas (RNA) update.

In some demonstrative embodiments, the RRC Resume Request message mayinclude a 16-bit resume Message Authentication Code for Integrity(resumeMAC-I) field, and/or a Resume Cause (ResumeCause) field, e.g., asdescribed below.

In some demonstrative embodiments, for example, first and second messageformats may be defined for the RRC Resume Request message. For example,the first and second RRC Resume Request message formats may have firstand second respective different CCCH sizes, e.g., as described below.

In some demonstrative embodiments, the first and second RRC ResumeRequest message formats may be configured to carry different informationand/or information fields of different lengths, e.g., as describedbelow.

In some demonstrative embodiments, the first predefined messageconfiguration e.g., the 48-bit CCCH message configuration, may include afirst Radio Resource Control (RRC) Resume Request (RRCResumeRequest)message configuration, and/or the second predefined messageconfiguration, e.g., the 64-bit CCCH message configuration, may includea second RRC Resume Request (RRCResumeRequest1) message configuration,e.g., as described below.

In some demonstrative embodiments, the first RRC Resume Request messageconfiguration may include a first resume identity (ResumeIdentity) fieldhaving a first predefined ResumeIdentity bit-size, and/or the second RRCResume Request message configuration may include a second resumeidentity field having a second predefined ResumeIdentity bit-size, forexample, shorter than the first predefined ResumeIdentity bit-size,e.g., as described below.

In some demonstrative embodiments, the second RRC Resume Request messageconfiguration may include a 40-bit resume identity (ResumeIdentity)field configured for a 40-bit Radio Network Temporary Identity (RNTI)value, and the first RRC Resume Request message configuration mayinclude a 16-bit resume identity field configured for a 16-bit truncatedRNTI value, e.g., as described below.

In one example, an I-RNTI-Value Information Element (IE) may be used toidentify a suspended UE context of a UE, e.g., UE 102, in an inactivestate, e.g., an RRC_INACTIVE state.

In other embodiments, the UL CCCH message may include any other RRCmessage and/or any other type of UL CCCH message, e.g., as describedbelow.

In some demonstrative embodiments, the UL CCCH message may include anRRC Setup Request (RRCSetupRequest), an RRC Reestablishment Request(RRCReestablishmentRequest), or an RRC System Information (Info) Request(RRCSystemInfoRequest), e.g., as described below. In other embodiments,any other additional or alternative RRC message may be defined.

In some demonstrative embodiments, UE 102 and/or gNB 140 may beconfigured to generate, communicate, transmit, receive, and/or processRRC messages of one or more RRC message types over an uplink CCCHlogical channel, for example, over a 64-bit UL CCCH (UL CCCH1), e.g., asdescribed below.

In some demonstrative embodiments, the one or more RRC message types maybe defined according to an UL message class (UL-CCCH1), which maydefined RRC message types to be communicated over the UL CCCH1 logicalchannel, e.g., as follows:

-  UL-CCCH1-Message The UL-CCCH1-Message class is the set of RRCmessages that may be sent from the UE to the Network on the uplink CCCH1logical channel. -- ASN1START -- TAG-UL-CCCH-MESSAGE-STARTUL-CCCH1-Message ::= SEQUENCE { message UL-CCCH1-MessageType }UL-CCCH1-MessageType ::= CHOICE { c1 CHOICE {  rrcSetupRequest1RRCSetupRequest1,  rrcResumeRequest1 RRCResumeRequest1, rrcReestablishmentRequest1 RRCReestablishmentRequest1, rrcSystemInfoRequest1 RRCSystemInfoRequest1  },  messageClassExtensionSEQUENCE { } } -- TAG-UL-CCCH-MESSAGE-STOP -- ASN1STOP

In some demonstrative embodiments, the UL-CCCH1-Message class may defineone or more CCCH message types, for example, a RRC Setup Request(RRCSetupRequest1), a RRC Resume Request (RRCResumeRequest1), a RRCReestablishment Request (RRCReestablishmentRequest1), and/or a RRCSystem Info Request (RRCSystemInfoRequest1).

In other embodiments, the UL CCCH message class may include or defineany other additional or alternative UL CCCH message types.

In some demonstrative embodiments, the RRCResumeRequest1 message may bedefined, e.g., as follows:

-   -   RRCResumeRequest1    -   The RRCResumeRequest1 message is used to request the resumption        of a suspended RRC connection or perform an RNA update.        -   Signalling radio bearer: SRB0        -   RLC-SAP: TM        -   Logical channel: CCCH1        -   Direction: UE to Network

RRCResumeRequest1 Message

-- ASN1START -- TAG-RRCRESUMEREQUEST1-START RRCResumeRequest1 ::=SEQUENCE { rrcResumeRequest1    RRCResumeRequest1-IEs }RRCResumeRequest1-IEs ::=  SEQUENCE {  resumeIdentity I-RNTI-Value,--40bits  resumeMAC-I BIT STRING (SIZE (16)),  resumeCause ResumeCause, spare BIT STRING (SIZE (1))  } ResumeCause ::= ENUMERATED { emergency,highPriorityAccess, mt-Access, mo-Signalling,mo-Data, mo-VoiceCall,rna-Update, spare1, spare2, spare3, spare4, spare5, spare6, spare7,spare8, spare9 } -- TAG-RRCRESUMEREQUEST1-STOP -- ASN1STOP

In other embodiments, the RRCResumeRequest1 may include any otherstructure, syntax, parameters, language and the like.

In one example, for example, the for a future study, theRRCResumeRequest1 may be configured to support one or more additionalresume causes, e.g., delayTolerantAccess, RNA Update, periodic RNAUpdate, MO video, MO SMS, and/or any other resume cause.

In some demonstrative embodiments, a 40-bit RNTI value in the 40-bitresume identity (ResumeIdentity) field in the RRCResumeRequest1 messagemay be defined, e.g., as follows:

-   -   I-RNTI-Value    -   The I-RNTI-Value IE is used to identify the suspended UE context        of a UE in RRC_INACTIVE.

I-RNTI-Value Information Element

-- ASN1START -- TAG-I-RNTI-VALUE-START I-RNTI-Value ::= BIT STRING(SIZE(40)) -- TAG-I-RNTI-VALUE-STOP -- ASN1STOP

In other embodiments, the 40-bit RNTI value in the RRCResumeRequest1message may include any other structure, syntax, parameters, languageand the like.

In some demonstrative embodiments, UE 102 and/or gNB 140 may beconfigured to communicate one or more RRC message types over an uplinkCCCH logical channel, for example, over a 48 bit UL CCCH, e.g., asdescribed below.

In some demonstrative embodiments, UE 102 and/or gNB 140 may beconfigured to communicate an RRC Resume Request (RRCResumeRequest)message over the 48-bit UL CCCH. In other embodiments, UE 102 and/or gNB140 may be configured to communicate any other type of messages over the48-bit UL CCCH.

For example, the RRCResumeRequest message, may be defined, e.g., asfollows:

-   -   RRCResumeRequest        -   Signalling radio bearer: SRB0        -   RLC-SAP: TM        -   Logical channel: CCCH        -   Direction: UE to Network

RRCResumeRequest Message

-- ASN1START -- TAG-RRCRESUMEREQUEST-START RRCResumeRequest ::= SEQUENCE{ rrcResumeRequest   RRCResumeRequest-IEs } RRCResumeRequest-IEs ::=SEQUENCE {  resumeIdentity truncated-i-RNTI BIT STRING (SIZE (24)), resumeMAC-I BIT STRING (SIZE (16)),  resumeCause ResumeCause,  spareBIT STRING (SIZE (1)) } -- FFS Which additional resume causes aresupported: delayTolerantAccess, RNA Update, periodic RNA Update, MOvideo, MO SMS, etc. ResumeCause ::= ENUMERATED { emergency,highPriorityAccess, mt-Access, mo- Signalling, mo-Data, mo-VoiceCall,rna-Update, spare1, spare2, spare3, spare4, spare5, spare6, spare7,spare8, spare9 } -- TAG-RRCRESUMEREQUEST-STOP -- ASN1STOP

In other embodiments, the RRC Resume Request (RRCResumeRequest) messagemay include any other structure, syntax, parameters, language and thelike.

In some demonstrative embodiments, UE 102 may be configured to selectbetween a 48-bit CCCH message configuration or a 64-bit CCCH messageconfiguration, to generate an UL CCCH message according to the selectedCCCH message configuration, and to transmit the UL CCCH message over aCCCH logical channel according to the selected CCCH messageconfiguration. For example, UE 102 may generate the RRCResumeRequest andtransmit the RRCResumeRequest over the UL CCCH logical channel, e.g.,when the 48-bit CCCH message configuration is selected; and/or UE 102may generate the RRCResumeRequest1 and transmit the RRCResumeRequest1over the UL CCCH1 logical channel, e.g., when the 64-bit CCCH messageconfiguration is selected, e.g., as described above.

In some demonstrative embodiments, UE 102 may set the resumeIdentityfield in the RRCResumeRequest message to include a 24-bit ID value,e.g., the truncated-i-RNTI, for example, when the 48-bit CCCH messageconfiguration is selected, e.g., as described above.

In some demonstrative embodiments, UE 102 may set the resumeIdentityfield in the RRCResumeRequest1 message to include a 40-bit ID value,e.g., the i-RNTI, for example, when the 64-bit CCCH messageconfiguration is selected, e.g., as described above.

Reference is made to FIG. 2 , which schematically illustrates anarchitecture of a system 200, in accordance with some demonstrativeembodiments. For example, one or more elements of system 100 (FIG. 1 )may perform one or more operations of, one or more functionalities of,and/or the role of, one or more elements of system 200.

In one example, system 200 may operate in conjunction with the Long TermEvolution (LTE) system standards and the 5G or NR system standards asprovided by 3GPP TS.

Some demonstrative embodiments are described herein with respect to a 5Gor NR system. However, other embodiments may be implemented with respectto any other system, communication scheme, network, standard and/orprotocol, for example, future 3GPP systems, e.g., Sixth Generation (6G))systems, IEEE 802.16 protocols, e.g., Wireless metropolitan areanetworks (MAN), Worldwide Interoperability for Microwave Access (WiMAX),and the like, or any other additional or alternative system and/ornetwork.

As shown by FIG. 2 , the system 200 may include user equipment (UE) 201a and UE 201 b (collectively referred to as “UEs 201” or “UE 201”).

In one example, UE 102 (FIG. 1 ) may perform one or more operations of,one or more functionalities of, and/or the role of, UE 201 a and/or UE201 b.

As used herein, the term “user equipment” or “UE” may refer to a devicewith radio communication capabilities and may describe a remote user ofnetwork resources in a communications network. The term “user equipment”or “UE” may be considered synonymous to, and may be referred to asclient, mobile, mobile device, mobile terminal, user terminal, mobileunit, mobile station, mobile user, subscriber, user, remote station,access agent, user agent, receiver, radio equipment, reconfigurableradio equipment, reconfigurable mobile device, etc. Furthermore, theterm “user equipment” or “UE” may include any type of wireless/wireddevice or any computing device including a wireless communicationsinterface.

In this example, UEs 201 are illustrated as smartphones (e.g., handheldtouchscreen mobile computing devices connectable to one or more cellularnetworks), but may also include any mobile or non-mobile computingdevice, such as consumer electronics devices, cellular phones,smartphones, feature phones, tablet computers, wearable computerdevices, Personal Digital Assistants (PDAs), pagers, wireless handsets,desktop computers, laptop computers, In-Vehicle Infotainment (IVI),in-car entertainment (ICE) devices, an Instrument Cluster (IC), Head-UpDisplay (HUD) devices, Onboard Diagnostic (OBD) devices, Dashtop MobileEquipment (DME), mobile data terminals (MDTs), Electronic EngineManagement System (EEMS), Electronic/Engine Control Units (ECUs),Electronic/Engine Control Modules (ECMs), embedded systems,microcontrollers, control modules, Engine Management Systems (EMS),networked or “smart” appliances, Machine-Type Communications (MTC)devices, Machine-To-Machine (M2M), Internet of Things (IoT) devices,and/or the like.

In some demonstrative embodiments, any of the UEs 201 may include an IoTUE, which may include a network access layer designed for low-power IoTapplications utilizing short-lived UE connections. An IoT UE may utilizetechnologies such as M2M or MTC for exchanging data with an MTC serveror device via a Public Land Mobile Network (PLMN), Proximity-BasedService (ProSe) or Device-To-Device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 201 may be configured to connect, for example, communicativelycouple, with an Access Network (AN) or Radio Access Network (RAN) 210.In embodiments, the RAN 210 may be a next Generation (NG) RAN or a 5GRAN, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), or a legacy RAN, such as aUTRAN (UMTS Terrestrial Radio Access Network) or GERAN (GSM (GlobalSystem for Mobile Communications or Groupe Special Mobile) EDGE (GSMEvolution) Radio Access Network). As used herein, the term “NG RAN” orthe like may refer to a RAN 210 that operates in an NR or 5G system 200,and the term “E-UTRAN” or the like may refer to a RAN 210 that operatesin an LTE or 4G system 200. The UEs 201 utilize connections (orchannels) 203 and 204, respectively, each of which includes a physicalcommunications interface or layer (discussed in further detail below).As used herein, the term “channel” may refer to any transmission medium,either tangible or intangible, which is used to communicate data or adata stream. The term “channel” may be synonymous with and/or equivalentto “communications channel,” “data communications channel,”“transmission channel,” “data transmission channel,” “access channel,”“data access channel,” “link,” “data link,” “carrier,” “radiofrequencycarrier,” and/or any other like term denoting a pathway or mediumthrough which data is communicated. Additionally, the term “link” mayrefer to a connection between two devices through a Radio AccessTechnology (RAT) for the purpose of transmitting and receivinginformation.

In one example, connections 104 (FIG. 1 ) may include connection 203and/or connection 204.

In this example, the connections 203 and 204 are illustrated as an airinterface to enable communicative coupling, and may be consistent withcellular communications protocols, such as a Global System for MobileCommunications (GSM) protocol, a Code-Division Multiple Access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and/or any of the othercommunications protocols discussed herein. In embodiments, the UEs 201may directly exchange communication data via a ProSe interface 205. TheProSe interface 205 may alternatively be referred to as a sidelink (SL)interface 205 and may include one or more logical channels, includingbut not limited to a Physical Sidelink Control Channel (PSCCH), aPhysical Sidelink Shared Channel (PSSCH), a Physical Sidelink DiscoveryChannel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

The UE 201 b is shown to be configured to access an access point (AP)206 (also referred to as also referred to as “WLAN node 206”, “WLAN206”, “WLAN Termination 206” or “WT 206” or the like) via connection207. The connection 207 may include a local wireless connection, such asa connection consistent with any IEEE 802.11 protocol, wherein the AP206 would include a WiFi® router. In this example, the AP 206 is shownto be connected to the Internet without connecting to the core networkof the wireless system (described in further detail below). In variousembodiments, the UE 201 b, RAN 210, and AP 206 may be configured toutilize LTE-WLAN aggregation (LWA) operation and/or WLAN LTE/WLAN RadioLevel Integration with IPsec Tunnel (LWIP) operation. The LWA operationmay involve the UE 201 b in RRC_CONNECTED being configured by a RAN node211 to utilize radio resources of LTE and WLAN. LWIP operation mayinvolve the UE 201 b using WLAN radio resources (e.g., connection 207)via Internet Protocol Security (IPsec) protocol tunneling toauthenticate and encrypt packets (e.g., internet protocol (IP) packets)sent over the connection 207. IPsec tunneling may include encapsulatingentirety of original IP packets and adding a new packet header therebyprotecting the original header of the IP packets.

The RAN 210 may include one or more AN nodes or RAN nodes 211 a and 211b (collectively referred to as “RAN nodes 211” or “RAN node 211”) thatenable the connections 203 and 204. As used herein, the terms “accessnode,” “access point,” or the like may describe equipment that providesthe radio baseband functions for data and/or voice connectivity betweena network and one or more users. These access nodes may be referred toas base stations (BS), next Generation NodeBs (gNBs), RAN nodes, evolvedNodeBs (eNBs), NodeBs, Road Side Units (RSUs), Transmission ReceptionPoints (TRxPs or TRPs), and so forth, and may include ground stations(e.g., terrestrial access points) or satellite stations providingcoverage within a geographic area (e.g., a cell). The term “Road SideUnit” or “RSU” may refer to any transportation infrastructure entityimplemented in or by an gNB/eNB/RAN node or a stationary (or relativelystationary) UE, where an RSU implemented in or by a UE may be referredto as a “UE-type RSU”, an RSU implemented in or by an eNB may bereferred to as an “eNB-type RSU.” As used herein, the term “NG RAN node”or the like may refer to a RAN node 211 that operates in an NR or 5Gsystem 200 (for example a gNB), and the term “E-UTRAN node” or the likemay refer to a RAN node 211 that operates in an LTE or 4G system 200(e.g., an eNB). According to various embodiments, the RAN nodes 211 maybe implemented as one or more of a dedicated physical device such as amacrocell base station, and/or a Low Power (LP) base station forproviding femtocells, picocells or other like cells having smallercoverage areas, smaller user capacity, or higher bandwidth compared tomacrocells. In other embodiments, the RAN nodes 211 may be implementedas one or more software entities running on server computers as part ofa virtual network, which may be referred to as a cloud radio accessnetwork (CRAN). In other embodiments, the RAN nodes 211 may representindividual gNB-distributed units (DUs) that are connected to agNB-centralized unit (CU) via an F1 interface (not shown by FIG. 2 ).

In one example, gNB 140 (FIG. 1 ) may perform one or more operations of,one or more functionalities of, and/or the role of, a RAN node of RANnodes 211, RAN node 211 a, and/or RAN node 211 b.

Any of the RAN nodes 211 may terminate the air interface protocol andmay be the first point of contact for the UEs 201. In some demonstrativeembodiments, any of the RAN nodes 211 may fulfill various logicalfunctions for the RAN 210 including, but not limited to, radio networkcontroller (RNC) functions such as radio bearer management, uplink anddownlink dynamic radio resource management and data packet scheduling,and mobility management.

In embodiments, the UEs 201 may be configured to communicate usingOrthogonal Frequency-Division Multiplexing (OFDM) communication signalswith each other or with any of the RAN nodes 211 over a multicarriercommunication channel in accordance various communication techniques,such as, but not limited to, an Orthogonal Frequency-Division MultipleAccess (OFDMA) communication technique (e.g., for downlinkcommunications) or a Single Carrier Frequency Division Multiple Access(SC-FDMA) communication technique, e.g., for uplink and ProSe orsidelink communications, although the scope of the embodiments is notlimited in this respect. The OFDM signals may include a plurality oforthogonal subcarriers.

In some demonstrative embodiments, a downlink resource grid may be usedfor downlink transmissions from any of the RAN nodes 211 to the UEs 201,while uplink transmissions may utilize similar techniques. The grid maybe a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid includes a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block includes a collection of resourceelements; in the frequency domain, this may represent the smallestquantity of resources that currently may be allocated. There are severaldifferent physical downlink channels that are conveyed using suchresource blocks.

According to various embodiments, the UEs 201, 202 and the RAN nodes211, 212 communicate data (for example, transmit and receive) data overa licensed medium (also referred to as the “licensed spectrum” and/orthe “licensed band”) and an unlicensed shared medium (also referred toas the “unlicensed spectrum” and/or the “unlicensed band”). The licensedspectrum may include channels that operate in the frequency range ofapproximately 400 MHz to approximately 3.8 GHz, whereas the unlicensedspectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs 201, 202 and the RANnodes 211, 212 may operate using Licensed Assisted Access (LAA),enhanced LAA (eLAA), and/or further eLAA (feLAA) mechanisms. In theseimplementations, the UEs 201, 202 and the RAN nodes 211, 212 may performone or more known medium-sensing operations and/or carrier-sensingoperations in order to determine whether one or more channels in theunlicensed spectrum is unavailable or otherwise occupied prior totransmitting in the unlicensed spectrum. The medium/carrier sensingoperations may be performed according to a listen-before-talk (LBT)protocol.

LBT is a mechanism whereby equipment (for example, UEs 201, 202, RANnodes 211, 212, etc.) senses a medium (for example, a channel or carrierfrequency) and transmits when the medium is sensed to be idle (or when aspecific channel in the medium is sensed to be unoccupied). The mediumsensing operation may include clear channel assessment (CCA), whichutilizes at least Energy Detection (ED) to determine the presence orabsence of other signals on a channel in order to determine if a channelis occupied or clear. This LBT mechanism allows cellular/LAA networks tocoexist with incumbent systems in the unlicensed spectrum and with otherLAA networks. ED may include sensing radiofrequency (RF) energy acrossan intended transmission band for a period of time and comparing thesensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based onIEEE 802.11 technologies. WLAN employs a contention-based channel accessmechanism, called Carrier Sense Multiple Access with Collision Avoidance(CSMA/CA). Here, when a WLAN node (e.g., a mobile station (MS) such asUE 201 or 202, AP 206, or the like) intends to transmit, the WLAN nodemay first perform CCA before transmission. Additionally, a backoffmechanism is used to avoid collisions in situations where more than oneWLAN node senses the channel as idle and transmits at the same time. Thebackoff mechanism may be a counter that is drawn randomly within theContention Window Size (CWS), which is increased exponentially upon theoccurrence of collision and reset to a minimum value when thetransmission succeeds. The LBT mechanism designed for LAA is somewhatsimilar to the CSMA/CA of WLAN. In some implementations, the LBTprocedure for DL or UL transmission bursts including PDSCH or PUSCHtransmissions, respectively, may have an LAA contention window that isvariable in length between X and Y Extended CCA (ECCA) slots, where Xand Y are minimum and maximum values for the CWSs for LAA. In oneexample, the minimum CWS for an LAA transmission may be 9 microseconds(μs); however, the size of the CWS and a Maximum Channel Occupancy Time(MCOT) (for example, a transmission burst) may be based on governmentalregulatory requirements.

The LAA mechanisms are built upon Carrier Aggregation (CA) technologiesof LTE-Advanced systems. In CA, each aggregated carrier is referred toas a Component Carrier (CC). A CC may have a bandwidth of 1.4, 3, 5, 10,15 or 20 MHz and a maximum of five CCs may be aggregated, and therefore,a maximum aggregated bandwidth is 100 MHz. In Frequency DivisionDuplexing (FDD) systems, the number of aggregated carriers may bedifferent for DL and UL, where the number of UL CCs is equal to or lowerthan the number of DL component carriers. In some cases, individual CCsmay have a different bandwidth than other CCs. In Time DivisionDuplexing (TDD) systems, the number of CCs as well as the bandwidths ofeach CC is usually the same for DL and UL.

CA also includes individual serving cells to provide individual CCs. Thecoverage of the serving cells may differ, for example, due to that CCson different frequency bands will experience different pathloss. Aprimary service cell or primary cell (PCell) may provide a Primary CC(PCC) for both UL and DL, and may handle Radio Resource Control (RRC)and Non-Access Stratum (NAS) related activities. The other serving cellsare referred to as secondary cells (SCells), and each SCell may providean individual Secondary CC (SCC) for both UL and DL. The SCCs may beadded and removed as required, while changing the PCC may require the UE201, 202 to undergo a handover. In LAA, eLAA, and feLAA, some or all ofthe SCells may operate in the unlicensed spectrum (referred to as “LAASCells”), and the LAA SCells are assisted by a PCell operating in thelicensed spectrum. When a UE is configured with more than one LAA SCell,the UE may receive UL grants on the configured LAA SCells indicatingdifferent Physical Uplink Shared Channel (PUSCH) starting positionswithin a same subframe.

The Physical Downlink Shared Channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 201. The Physical Downlink ControlChannel (PDCCH) may carry information about the transport format andresource allocations related to the PDSCH channel, among other things.It may also inform the UEs 201 about the transport format, resourceallocation, and Hybrid Automatic Repeat Request (H-ARQ) informationrelated to the uplink shared channel. Typically, downlink scheduling(assigning control and shared channel resource blocks to the UE 201 bwithin a cell) may be performed at any of the RAN nodes 211 based onchannel quality information fed back from any of the UEs 201. Thedownlink resource assignment information may be sent on the PDCCH usedfor (e.g., assigned to) each of the UEs 201.

The PDCCH may use Control Channel Elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH may betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There maybe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore Enhanced the Control Channel Elements (ECCEs). Similar to above,each ECCE may correspond to nine sets of four physical resource elementsknown as an Enhanced Resource Element Groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

The RAN nodes 211 may be configured to communicate with one another viainterface 212. In embodiments where the system 200 is an LTE system, theinterface 212 may be an X2 interface 212. The X2 interface may bedefined between two or more RAN nodes 211 (e.g., two or more eNBs andthe like) that connect to EPC 120, and/or between two eNBs connecting toEPC 120. In some implementations, the X2 interface may include an X2user plane interface (X2-U) and an X2 control plane interface (X2-C).The X2-U may provide flow control mechanisms for user data packetstransferred over the X2 interface, and may be used to communicateinformation about the delivery of user data between eNBs. For example,the X2-U may provide specific sequence number information for user datatransferred from a master eNB (MeNB) to a secondary eNB (SeNB);information about successful in sequence delivery of PDCP PDUs to a UE201 from an SeNB for user data; information of PDCP PDUs that were notdelivered to a UE 201; information about a current minimum desiredbuffer size at the SeNB for transmitting to the UE user data; and thelike. The X2-C may provide intra-LTE access mobility functionality,including context transfers from source to target eNBs, user planetransport control, etc.; load management functionality; as well asinter-cell interference coordination functionality.

In embodiments where the system 200 is a 5G or NR system, the interface212 may be an Xn interface 212. The Xn interface is defined between twoor more RAN nodes 211 (e.g., two or more gNBs and the like) that connectto 5GC 220, between a RAN node 211 (e.g., a gNB) connecting to 5GC 220and an eNB, and/or between two eNBs connecting to 5GC 220. In someimplementations, the Xn interface may include an Xn user plane (Xn-U)interface and an Xn control plane (Xn-C) interface. The Xn-U may providenon-guaranteed delivery of user plane PDUs and support/provide dataforwarding and flow control functionality. The Xn-C may providemanagement and error handling functionality, functionality to manage theXn-C interface; mobility support for UE 201 in a connected mode (e.g.,CM-CONNECTED) including functionality to manage the UE mobility forconnected mode between one or more RAN nodes 211. The mobility supportmay include context transfer from an old (source) serving RAN node 211to new (target) serving RAN node 211; and control of user plane tunnelsbetween old (source) serving RAN node 211 to new (target) serving RANnode 211. A protocol stack of the Xn-U may include a transport networklayer built on Internet Protocol (IP) transport layer, and a GTP-U layeron top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-Cprotocol stack may include an application layer signaling protocol(referred to as Xn Application Protocol (Xn-AP)) and a transport networklayer that is built on SCTP. The SCTP may be on top of an IP layer, andmay provide the guaranteed delivery of application layer messages. Inthe transport IP layer point-to-point transmission is used to deliverthe signaling PDUs. In other implementations, the Xn-U protocol stackand/or the Xn-C protocol stack may be same or similar to the user planeand/or control plane protocol stack(s) shown and described herein.

The RAN 210 is shown to be communicatively coupled to a core network 220in this embodiment, Core Network (CN) 220. The CN 220 may include aplurality of network elements 222, which are configured to offer variousdata and telecommunications services to customers/subscribers (e.g.,users of UEs 201) who are connected to the CN 220 via the RAN 210. Theterm “network element” may describe a physical or virtualized equipmentused to provide wired or wireless communication network services. Theterm “network element” may be considered synonymous to and/or referredto as a networked computer, networking hardware, network equipment,router, switch, hub, bridge, radio network controller, radio accessnetwork device, gateway, server, virtualized network function (VNF),Network Functions Virtualization Infrastructure (NFVI), and/or the like.The components of the CN 220 may be implemented in one physical node orseparate physical nodes including components to read and executeinstructions from a machine-readable or computer-readable medium (e.g.,a non-transitory machine-readable storage medium). In some demonstrativeembodiments, Network Functions Virtualization (NFV) may be utilized tovirtualize any or all of the above described network node functions viaexecutable instructions stored in one or more computer readable storagemediums (described in further detail below). A logical instantiation ofthe CN 220 may be referred to as a network slice, and a logicalinstantiation of a portion of the CN 220 may be referred to as a networksub-slice. NFV architectures and infrastructures may be used tovirtualize one or more network functions, alternatively performed byproprietary hardware, onto physical resources including a combination ofindustry-standard server hardware, storage hardware, or switches. Inother words, NFV systems may be used to execute virtual orreconfigurable implementations of one or more EPC components/functions.

Generally, the application server 230 may be an element offeringapplications that use IP bearer resources with the core network (e.g.,UMTS Packet Services (PS) domain, LTE PS data services, etc.). Theapplication server 230 may also be configured to support one or morecommunication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 201 via the EPC 220.

In embodiments, the CN 220 may be a 5GC (referred to as “5GC 220” or thelike), and the RAN 210 may be connected with the CN 220 via an NGinterface 213. In embodiments, the NG interface 213 may be split intotwo parts, an NG user plane (NG-U) interface 214, which carries trafficdata between the RAN nodes 211 and a user plane function (UPF), and theS1 control plane (NG-C) interface 215, which is a signaling interfacebetween the RAN nodes 211 and Access and Mobility Functions (AMFs). Inembodiments, the CN 220 may be a 5G CN (referred to as “5GC 220” or thelike), while in other embodiments, the CN 220 may be an Evolved PacketCore (EPC)). Where CN 220 is an EPC (referred to as “EPC 220” or thelike), the RAN 210 may be connected with the CN 220 via an S1 interface213. In embodiments, the S1 interface 23 may be split into two parts, anS1 user plane (S1-U) interface 214, which carries traffic data betweenthe RAN nodes 211 and the serving gateway (S-GW), and the S1-MobilityManagement Entity (MME) interface 215, which is a signaling interfacebetween the RAN nodes 211 and MMEs.

Reference is made to FIG. 3 , which schematically illustrates aninfrastructure equipment 300, in accordance with some demonstrativeembodiments.

In one example, the infrastructure equipment 300 (or “system 300”) maybe implemented as a base station, radio head, RAN node, etc., such asthe RAN nodes 211 and/or AP 206 (FIG. 2 ) shown and describedpreviously. For example, gNB 140 (FIG. 1 ) may include some or allcomponents and/or elements of infrastructure equipment 300.

In other example, the system 300 could be implemented in or by a UE,application server(s) 230, and/or any other element/device discussedherein.

The system 300 may include one or more of application circuitry 305,baseband circuitry 310, one or more radio front end modules 315, memory320, power management integrated circuitry (PMIC) 325, power teecircuitry 330, network controller 335, network interface connector 340,satellite positioning circuitry 345, and user interface 350. In somedemonstrative embodiments, the device 300 may include additionalelements such as, for example, memory/storage, display, camera, sensor,or Input/Output (I/O) interface. In other embodiments, the componentsdescribed below may be included in more than one device (e.g., thecircuitries may be separately included in more than one device forCloud-RAN (C-RAN) implementations).

As used herein, the term “circuitry” may refer to, is part of, orincludes hardware components such as an electronic circuit, a logiccircuit, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group), an Application Specific IntegratedCircuit (ASIC), a Field-Programmable Device (FPD), (e.g., aField-Programmable Gate Array (FPGA), a Programmable Logic Device (PLD),a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, ora programmable System on Chip (SoC)), digital signal processors (DSPs),etc., that are configured to provide the described functionality. Insome demonstrative embodiments, the circuitry may execute one or moresoftware or firmware programs to provide at least some of the describedfunctionality. In addition, the term “circuitry” may also refer to acombination of one or more hardware elements (or a combination ofcircuits used in an electrical or electronic system) with the programcode used to carry out the functionality of that program code. In theseembodiments, the combination of hardware elements and program code maybe referred to as a particular type of circuitry.

The terms “application circuitry” and/or “baseband circuitry” may beconsidered synonymous to, and may be referred to as “processorcircuitry.” As used herein, the term “processor circuitry” may refer to,is part of, or includes circuitry capable of sequentially andautomatically carrying out a sequence of arithmetic or logicaloperations; recording, storing, and/or transferring digital data. Theterm “processor circuitry” may refer to one or more applicationprocessors, one or more baseband processors, and a physical centralprocessing unit (CPU), a single-core processor, a dual-core processor, atriple-core processor, a quad-core processor, and/or any other devicecapable of executing or otherwise operating computer-executableinstructions, such as program code, software modules, and/or functionalprocesses.

Furthermore, the various components of the core network 220 (FIG. 2 )may be referred to as “network elements.” The term “network element” maydescribe a physical or virtualized equipment used to provide wired orwireless communication network services. The term “network element” maybe considered synonymous to and/or referred to as a networked computer,networking hardware, network equipment, network node, router, switch,hub, bridge, radio network controller, radio access network device,gateway, server, virtualized network function (VNF), network functionsvirtualization infrastructure (NFVI), and/or the like.

Application circuitry 305 may include one or more central processingunit (CPU) cores and one or more of cache memory, Low Drop-Out voltageregulators (LDOs), interrupt controllers, serial interfaces such as SPI,I2C or universal programmable serial interface module, Real Time Clock(RTC), timer-counters including interval and watchdog timers, generalpurpose input/output (I/O or IO), memory card controllers such as SecureDigital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB)interfaces, Mobile Industry Processor Interface (MIPI) interfaces andJoint Test Access Group (JTAG) test access ports. As examples, theapplication circuitry 305 may include one or more Intel Pentium®, Core®,or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s),Accelerated Processing Units (APUs), or Epyc® processors; and/or thelike. In some demonstrative embodiments, the system 300 may not utilizeapplication circuitry 305, and instead may include a special-purposeprocessor/controller to process IP data received from an EPC or SGC, forexample.

Additionally or alternatively, application circuitry 305 may includecircuitry such as, but not limited to, one or more a field-programmabledevices (FPDs) such as field-programmable gate arrays (FPGAs) and thelike; programmable logic devices (PLDs) such as complex PLDs (CPLDs),high-capacity PLDs (HCPLDs), and the like; ASICs such as structuredASICs and the like; programmable SoCs (PSoCs); and the like. In suchembodiments, the circuitry of application circuitry 305 may includelogic blocks or logic fabric including and other interconnectedresources that may be programmed to perform various functions, such asthe procedures, methods, functions, etc. of the various embodimentsdiscussed herein. In such embodiments, the circuitry of applicationcircuitry 305 may include memory cells (e.g., erasable programmableread-only memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM), flash memory, static memory (e.g., Static Random AccessMemory (SRAM), anti-fuses, etc.) used to store logic blocks, logicfabric, data, etc. in Lookup-Tables (LUTs) and the like.

The baseband circuitry 310 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Althoughnot shown, baseband circuitry 310 may include one or more digitalbaseband systems, which may be coupled via an interconnect subsystem toa CPU subsystem, an audio subsystem, and an interface subsystem. Thedigital baseband subsystems may also be coupled to a digital basebandinterface and a mixed-signal baseband sub-system via anotherinterconnect subsystem. Each of the interconnect subsystems may includea bus system, point-to-point connections, Network-On-Chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed herein. The audio sub-system may include digitalsignal processing circuitry, buffer memory, program memory, speechprocessing accelerator circuitry, data converter circuitry such asanalog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, and/or otherlike components. In an aspect of the present disclosure, basebandcircuitry 310 may include protocol processing circuitry with one or moreinstances of control circuitry (not shown) to provide control functionsfor the digital baseband circuitry and/or radio frequency circuitry(e.g., the radio front end modules 315).

User interface circuitry 350 may include one or more user interfacesdesigned to enable user interaction with the system 300 or peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 300. User interfaces may include, but are not limited toone or more physical or virtual buttons (e.g., a reset button), one ormore indicators (e.g., Light Emitting Diodes (LEDs)), a physicalkeyboard or keypad, a mouse, a touchpad, a touchscreen, speakers orother audio emitting devices, microphones, a printer, a scanner, aheadset, a display screen or display device, etc. Peripheral componentinterfaces may include, but are not limited to, a non-volatile memoryport, a universal serial bus (USB) port, an audio jack, a power supplyinterface, etc.

The Radio Front End Modules (RFEMs) 315 may include a millimeter waveRFEM and one or more sub-millimeter wave Radio Frequency IntegratedCircuits (RFICs). In some implementations, the one or moresub-millimeter wave RFICs may be physically separated from themillimeter wave RFEM. The RFICs may include connections to one or moreantennas or antenna arrays, and the RFEM may be connected to multipleantennas. In alternative implementations, both millimeter wave andsub-millimeter wave radio functions may be implemented in the samephysical radio front end module 315. The RFEMs 315 may incorporate bothmillimeter wave antennas and sub-millimeter wave antennas.

The memory circuitry 320 may include one or more of volatile memoryincluding Dynamic Random Access Memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and Nonvolatile Memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), Phase Change Random Access Memory (PRAM), MagnetoresistiveRandom Access Memory (MRAM), etc., and may incorporate thethree-dimensional (3D) cross-point (XPOINT) memories from Intel® andMicron®. Memory circuitry 320 may be implemented as one or more ofsolder down packaged integrated circuits, socketed memory modules andplug-in memory cards.

The PMIC 325 may include voltage regulators, surge protectors, poweralarm detection circuitry, and one or more backup power sources such asa battery or capacitor. The power alarm detection circuitry may detectone or more of brown out (under-voltage) and surge (over-voltage)conditions. The power tee circuitry 330 may provide for electrical powerdrawn from a network cable to provide both power supply and dataconnectivity to the infrastructure equipment 300 using a single cable.

The network controller circuitry 335 may provide connectivity to anetwork using a standard network interface protocol such as Ethernet,Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching(MPLS), or some other suitable protocol. Network connectivity may beprovided to/from the infrastructure equipment 300 via network interfaceconnector 340 using a physical connection, which may be electrical(commonly referred to as a “copper interconnect”), optical, or wireless.The network controller circuitry 335 may include one or more dedicatedprocessors and/or FPGAs to communicate using one or more of theaforementioned protocols. In some implementations, the networkcontroller circuitry 335 may include multiple controllers to provideconnectivity to other networks using the same or different protocols.

The positioning circuitry 345, which may include circuitry to receiveand decode signals transmitted by one or more navigation satelliteconstellations of a global navigation satellite system (GNSS). Examplesof navigation satellite constellations (or GNSS) may include UnitedStates' Global Positioning System (GPS), Russia's Global NavigationSystem (GLONASS), the European Union's Galileo system, China's BeiDouNavigation Satellite System, a regional navigation system or GNSSaugmentation system (e.g., Navigation with Indian Constellation (NAVIC),Japan's Quasi-Zenith Satellite System (QZSS), France's DopplerOrbitography and Radio-positioning Integrated by Satellite (DORIS),etc.), or the like. The positioning circuitry 345 may include varioushardware elements (e.g., including hardware devices such as switches,filters, amplifiers, antenna elements, and the like to facilitate thecommunications over-the-air (OTA) communications) to communicate withcomponents of a positioning network, such as navigation satelliteconstellation nodes.

Nodes or satellites of the navigation satellite constellation(s) (“GNSSnodes”) may provide positioning services by continuously transmitting orbroadcasting GNSS signals along a line of sight, which may be used byGNSS receivers (e.g., positioning circuitry 345 and/or positioningcircuitry implemented by UEs 201, 202, or the like) to determine theirGNSS position. The GNSS signals may include a pseudorandom code (e.g., asequence of ones and zeros) that is known to the GNSS receiver and amessage that includes a time of transmission (ToT) of a code epoch(e.g., a defined point in the pseudorandom code sequence) and the GNSSnode position at the ToT. The GNSS receivers may monitor/measure theGNSS signals transmitted/broadcasted by a plurality of GNSS nodes (e.g.,four or more satellites) and solve various equations to determine acorresponding GNSS position (e.g., a spatial coordinate). The GNSSreceivers also implement clocks that are typically less stable and lessprecise than the atomic clocks of the GNSS nodes, and the GNSS receiversmay use the measured GNSS signals to determine the GNSS receivers'deviation from true time (e.g., an offset of the GNSS receiver clockrelative to the GNSS node time). In some demonstrative embodiments, thepositioning circuitry 345 may include a Micro-Technology forPositioning, Navigation, and Timing (Micro-PNT) IC that uses a mastertiming clock to perform position tracking/estimation without GNSSassistance.

The GNSS receivers may measure the time of arrivals (ToAs) of the GNSSsignals from the plurality of GNSS nodes according to its own clock. TheGNSS receivers may determine ToF values for each received GNSS signalfrom the ToAs and the ToTs, and then may determine, from the ToFs, athree-dimensional (3D) position and clock deviation. The 3D position maythen be converted into a latitude, longitude and altitude. Thepositioning circuitry 345 may provide data to application circuitry 305which may include one or more of position data or time data. Applicationcircuitry 305 may use the time data to synchronize operations with otherradio base stations (e.g., RAN nodes 211 or the like).

The components shown by FIG. 3 may communicate with one another usinginterface circuitry. As used herein, the term “interface circuitry” mayrefer to, is part of, or includes circuitry providing for the exchangeof information between two or more components or devices. The term“interface circuitry” may refer to one or more hardware interfaces, forexample, buses, Input/Output (I/O) interfaces, peripheral componentinterfaces, network interface cards, and/or the like. Any suitable bustechnology may be used in various implementations, which may include anynumber of technologies, including Industry Standard Architecture (ISA),Extended ISA (EISA), Peripheral Component Interconnect (PCI), PeripheralComponent Interconnect Extended (PCIx), PCI express (PCIe), or anynumber of other technologies. The bus may be a proprietary bus, forexample, used in a SoC based system. Other bus systems may be included,such as an I2C interface, an SPI interface, point to point interfaces,and a power bus, among others.

Reference is made to FIG. 4 , which schematically illustrates elementsof a platform 400, in accordance with some demonstrative embodiments.

In one example, one or more elements of platform 400 may be configuredto perform one or more functionalities of one or more of radio 114 (FIG.1 ), controller 128 (FIG. 1 ), message processor 128 (FIG. 1 ), and/orone or more other elements of UE 102 (FIG. 1 ).

In one example, device 400 may be suitable for use as UEs 201, 202,application servers 230, (FIG. 2 ) and/or any other element/devicediscussed herein. The platform 400 may include any combinations of thecomponents shown in the example. The components of platform 400 may beimplemented as Integrated Circuits (ICs), portions thereof, discreteelectronic devices, or other modules, logic, hardware, software,firmware, or a combination thereof adapted in the computer platform 400,or as components otherwise incorporated within a chassis of a largersystem. The block diagram of FIG. 4 is intended to show a high levelview of components of the computer platform 400. However, some of thecomponents shown may be omitted, additional components may be present,and different arrangement of the components shown may occur in otherimplementations.

The application circuitry 405 may include circuitry such as, but notlimited to single-core or multi-core processors and one or more of cachememory, Low Drop-Out Voltage Regulators (LDOs), interrupt controllers,serial interfaces such as serial peripheral interface (SPI),Inter-Integrated Circuit (I2C) or universal programmable serialinterface circuit, Real Time Clock (RTC), timer-counters includinginterval and watchdog timers, general purpose input-output (IO), memorycard controllers such as Secure Digital/Multi-Media Card (SD/MMC) orsimilar, Universal Serial Bus (USB) interfaces, mobile industryprocessor interface (MIPI) interfaces and Joint Test Access Group (JTAG)test access ports. The processor(s) may include any combination ofgeneral-purpose processors and/or dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors (or cores) maybe coupled with or may include memory/storage and may be configured toexecute instructions stored in the memory/storage to enable variousapplications or operating systems to run on the platform 400. In somedemonstrative embodiments, processors of application circuitry 305/405may process IP data packets received from an EPC or SGC.

Application circuitry 405 be or include a microprocessor, a multi-coreprocessor, a multithreaded processor, an ultra-low voltage processor, anembedded processor, or other known processing element. In one example,the application circuitry 405 may include an Intel® Architecture Core™based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or anMCU-class processor, or another such processor available from Intel®Corporation, Santa Clara, Calif. The processors of the applicationcircuitry 405 may also be one or more of Advanced Micro Devices (AMD)Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm®Technologies, Inc., Texas Instruments, Inc.® Open MultimediaApplications Platform (OMAP)™ processor(s); a MIPS-based design fromMIPS Technologies, Inc; an ARM-based design licensed from ARM Holdings,Ltd.; or the like. In some implementations, the application circuitry405 may be a part of a system on a chip (SoC) in which the applicationcircuitry 405 and other components are formed into a single integratedcircuit, or a single package, such as the Edison™ or Galileo™ SoC boardsfrom Intel® Corporation.

Additionally or alternatively, application circuitry 405 may includecircuitry such as, but not limited to, one or more a Field-ProgrammableDevices (FPDs) such as FPGAs and the like; Programmable Logic Devices(PLDs) such as complex PLDs (CPLDs), High-Capacity PLDs (HCPLDs), andthe like; ASICs such as structured ASICs and the like; programmable SoCs(PSoCs); and the like. In such embodiments, the circuitry of applicationcircuitry 405 may include logic blocks or logic fabric including andother interconnected resources that may be programmed to perform variousfunctions, such as the procedures, methods, functions, etc. of thevarious embodiments discussed herein. In such embodiments, the circuitryof application circuitry 405 may include memory cells (e.g., erasableprogrammable read-only memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), flash memory, static memory(e.g., Static Random Access Memory (SRAM), anti-fuses, etc.) used tostore logic blocks, logic fabric, data, etc. in Lookup-Tables (LUTs) andthe like.

The baseband circuitry 410 may be implemented, for example, as asolder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits. Althoughnot shown, baseband circuitry 410 may include one or more digitalbaseband systems, which may be coupled via an interconnect subsystem toa CPU subsystem, an audio subsystem, and an interface subsystem. Thedigital baseband subsystems may also be coupled to a digital basebandinterface and a mixed-signal baseband sub-system via anotherinterconnect subsystem. Each of the interconnect subsystems may includea bus system, point-to-point connections, Network-On-Chip (NOC)structures, and/or some other suitable bus or interconnect technology,such as those discussed herein. The audio sub-system may include digitalsignal processing circuitry, buffer memory, program memory, speechprocessing accelerator circuitry, data converter circuitry such asanalog-to-digital and digital-to-analog converter circuitry, analogcircuitry including one or more of amplifiers and filters, and/or otherlike components. In an aspect of the present disclosure, basebandcircuitry 410 may include protocol processing circuitry with one or moreinstances of control circuitry (not shown) to provide control functionsfor the digital baseband circuitry and/or radio frequency circuitry(e.g., the radio front end modules 415).

The Radio Front End Modules (RFEMs) 415 may include a millimeter waveRFEM and one or more sub-millimeter wave Radio Frequency IntegratedCircuits (RFICs). In some implementations, the one or moresub-millimeter wave RFICs may be physically separated from themillimeter wave RFEM. The RFICs may include connections to one or moreantennas or antenna arrays, and the RFEM may be connected to multipleantennas. In alternative implementations, both millimeter wave andsub-millimeter wave radio functions may be implemented in the samephysical radio front end module 415. The RFEMs 415 may incorporate bothmillimeter wave antennas and sub-millimeter wave antennas.

The memory circuitry 420 may include any number and type of memorydevices used to provide for a given amount of system memory. Asexamples, the memory circuitry 420 may include one or more of volatilememory including be Random Access Memory (RAM), dynamic RAM (DRAM)and/or Synchronous Dynamic RAM (SDRAM), and nonvolatile memory (NVM)including high-speed electrically erasable memory (commonly referred toas Flash memory), phase change random access memory (PRAM),Magnetoresistive Random Access Memory (MRAM), etc. The memory circuitry420 may be developed in accordance with a JOINT ELECTRON DEVICESENGINEERING COUNCIL (JEDEC) low power double data rate (LPDDR)-baseddesign, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry420 may be implemented as one or more of solder down packaged integratedcircuits, Single Die Package (SDP), Dual Die Package (DDP) or Quad DiePackage (Q17P), socketed memory modules, Dual Inline Memory Modules(DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto amotherboard via a Ball Grid Array (BGA). In low power implementations,the memory circuitry 420 may be on-die memory or registers associatedwith the application circuitry 405. To provide for persistent storage ofinformation such as data, applications, operating systems and so forth,memory circuitry 420 may include one or more mass storage devices, whichmay include, inter alia, a solid state disk drive (SSDD), Hard DiskDrive (HDD), a micro HDD, resistance change memories, phase changememories, holographic memories, or chemical memories, among others. Forexample, the computer platform 400 may incorporate the Three-Dimensional(3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry 423 may include devices, circuitry,enclosures/housings, ports or receptacles, etc. used to coupled portabledata storage devices with the platform 400. These portable data storagedevices may be used for mass storage purposes, and may include, forexample, flash memory cards (e.g., Secure Digital (SD) cards, microSDcards, xD picture cards, and the like), and USB flash drives, opticaldiscs, external HDDs, and the like.

The platform 400 may also include interface circuitry (not shown) thatis used to connect external devices with the platform 400. The externaldevices connected to the platform 400 via the interface circuitry mayinclude sensors 421, such as accelerometers, level sensors, flowsensors, temperature sensors, pressure sensors, barometric pressuresensors, and the like. The interface circuitry may be used to connectthe platform 400 to electro-mechanical components (EMCs) 422, which mayallow platform 400 to change its state, position, and/or orientation, ormove or control a mechanism or system. The EMCs 422 may include one ormore power switches, relays including Electromechanical Relays (EMRs)and/or Solid State Relays (SSRs), actuators (e.g., valve actuators,etc.), an audible sound generator, a visual warning device, motors(e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers,claws, clamps, hooks, and/or other like electro-mechanical components.In embodiments, platform 400 may be configured to operate one or moreEMCs 422 based on one or more captured events and/or instructions orcontrol signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect theplatform 400 with positioning circuitry 445, which may be the same orsimilar as the positioning circuitry 345 discussed with regard to FIG. 3.

In some implementations, the interface circuitry may connect theplatform 400 with near-field communication (NFC) circuitry 440, whichmay include an NFC controller coupled with an antenna element and aprocessing device. The NFC circuitry 440 may be configured to readelectronic tags and/or connect with another NFC-enabled device.

The driver circuitry 446 may include software and hardware elements thatoperate to control particular devices that are embedded in the platform400, attached to the platform 400, or otherwise communicatively coupledwith the platform 400. The driver circuitry 446 may include individualdrivers allowing other components of the platform 400 to interact orcontrol various input/output (I/O) devices that may be present within,or connected to, the platform 400. For example, driver circuitry 446 mayinclude a display driver to control and allow access to a displaydevice, a touchscreen driver to control and allow access to atouchscreen interface of the platform 400, sensor drivers to obtainsensor readings of sensors 421 and control and allow access to sensors421, EMC drivers to obtain actuator positions of the EMCs 422 and/orcontrol and allow access to the EMCs 422, a camera driver to control andallow access to an embedded image capture device, audio drivers tocontrol and allow access to one or more audio devices.

The power management integrated circuitry (PMIC) 425 (also referred toas “power management circuitry 425”) may manage power provided tovarious components of the platform 400. In particular, with respect tothe baseband circuitry 410, the PMIC 425 may control power-sourceselection, voltage scaling, battery charging, or DC-to-DC conversion.The PMIC 425 may often be included when the platform 400 is capable ofbeing powered by a battery 430, for example, when the device is includedin a UE 201, 202.

In some demonstrative embodiments, the PMIC 425 may control, orotherwise be part of, various power saving mechanisms of the platform400. For example, if the platform 400 is in an RRC_Connected state,where it is still connected to the RAN node as it expects to receivetraffic shortly, then it may enter a state known as DiscontinuousReception Mode (DRX) after a period of inactivity. During this state,the platform 400 may power down for brief intervals of time and thussave power. If there is no data traffic activity for an extended periodof time, then the platform 400 may transition off to an RRC_Idle state,where it disconnects from the network and does not perform operationssuch as channel quality feedback, handover, etc. The platform 400 goesinto a very low power state and it performs paging where again itperiodically wakes up to listen to the network and then powers downagain. The platform 400 may not receive data in this state, in order toreceive data, it must transition back to RRC_Connected state. Anadditional power saving mode may allow a device to be unavailable to thenetwork for periods longer than a paging interval (ranging from secondsto a few hours). During this time, the device is totally unreachable tothe network and may power down completely. Any data sent during thistime incurs a large delay and it is assumed the delay is acceptable.

A battery 430 may power the platform 400, although in some examples theplatform 400 may be mounted deployed in a fixed location, and may have apower supply coupled to an electrical grid. The battery 430 may be alithium ion battery, a metal-air battery, such as a zinc-air battery, analuminum-air battery, a lithium-air battery, and the like. In someimplementations, such as in V2X applications, the battery 430 may be atypical lead-acid automotive battery.

In some implementations, the battery 430 may be a “smart battery,” whichincludes or is coupled with a Battery Management System (BMS) or batterymonitoring integrated circuitry. The BMS may be included in the platform400 to track the state of charge (SoCh) of the battery 430. The BMS maybe used to monitor other parameters of the battery 430 to providefailure predictions, such as the State Of Health (SoH) and the State OfFunction (SoF) of the battery 430. The BMS may communicate theinformation of the battery 430 to the application circuitry 405 or othercomponents of the platform 400. The BMS may also include anAnalog-To-Digital Convertor (ADC) that allows the application circuitry405 to directly monitor the voltage of the battery 430 or the currentflow from the battery 430. The battery parameters may be used todetermine actions that the platform 400 may perform, such astransmission frequency, network operation, sensing frequency, and thelike.

A power block, or other power supply coupled to an electrical grid maybe coupled with the BMS to charge the battery 430. In some examples, thepower block 228 may be replaced with a wireless power receiver to obtainthe power wirelessly, for example, through a loop antenna in thecomputer platform 400. In these examples, a wireless battery chargingcircuit may be included in the BMS. The specific charging circuitschosen may depend on the size of the battery 430, and thus, the currentrequired. The charging may be performed using the Airfuel standardpromulgated by the Airfuel Alliance, the Qi wireless charging standardpromulgated by the Wireless Power Consortium, or the Rezence chargingstandard, promulgated by the Alliance for Wireless Power, among others.

Although not shown, the components of platform 400 may communicate withone another using a suitable bus technology, which may include anynumber of technologies, including industry standard architecture (ISA),extended ISA (EISA), peripheral component interconnect (PCI), PeripheralComponent Interconnect Extended (PCIx), PCI express (PCIe), aTime-Trigger Protocol (TTP) system, or a FlexRay system, or any numberof other technologies. The bus may be a proprietary bus, for example,used in a SoC based system. Other bus systems may be included, such asan I2C interface, an SPI interface, point to point interfaces, and apower bus, among others.

Reference is made to FIG. 5 , which schematically illustrates a basebandand Radio Frequency (RF) configuration 500, in accordance with somedemonstrative embodiments.

In one example, UE 102 (FIG. 1 ) and/or gNB 140 (FIG. 1 ), may includeone or more elements of RF/baseband configuration 500.

In one example, the elements and/or components of configuration 500 maybe included as part of baseband circuitry 310 (FIG. 3 ) and/or 410 (FIG.4 ) and/or radio front end modules (RFEM) 315 (FIG. 3 ) and/or 415 (FIG.4 ).

As shown, the RFEM 315/415 may include Radio Frequency (RF) circuitry506, front-end module (FEM) circuitry 508, one or more antennas 511coupled together at least as shown.

The baseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 ) may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The baseband circuitry 310 (FIG. 3 ) and/or 410(FIG. 4 ) may include one or more baseband processors or control logicto process baseband signals received from a receive signal path of theRF circuitry 506 and to generate baseband signals for a transmit signalpath of the RF circuitry 506. Baseband processing circuitry 310 (FIG. 3) and/or 410 (FIG. 4 ) may interface with the application circuitry305/405 for generation and processing of the baseband signals and forcontrolling operations of the RF circuitry 506. For example, in someembodiments, the baseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 )may include a third generation (3G) baseband processor 504A, a fourthgeneration (4G) baseband processor 504B, a fifth generation (5G)baseband processor 504C, or other baseband processor(s) 504D for otherexisting generations, generations in development or to be developed inthe future (e.g., second generation (2G), sixth generation (6G), etc.).The baseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 ) (e.g., one ormore of baseband processors 504A-D) may handle various radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 506. In other embodiments, some or all of thefunctionality of baseband processors 504A-D may be included in modulesstored in the memory 504G and executed via a Central Processing Unit(CPU) 504E. The radio control functions may include, but are not limitedto, signal modulation/demodulation, encoding/decoding, radio frequencyshifting, etc. In some demonstrative embodiments,modulation/demodulation circuitry of the baseband circuitry 310 (FIG. 3) and/or 410 (FIG. 4 ) may include Fast-Fourier Transform (FFT),precoding, or constellation mapping/demapping functionality. In somedemonstrative embodiments, encoding/decoding circuitry of the basebandcircuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 ) may include convolution,tail-biting convolution, turbo, Viterbi, or Low Density Parity Check(LDPC) encoder/decoder functionality. Embodiments ofmodulation/demodulation and encoder/decoder functionality are notlimited to these examples and may include other suitable functionalityin other embodiments.

In some demonstrative embodiments, the baseband circuitry 310 (FIG. 3 )and/or 410 (FIG. 4 ) may include one or more audio Digital SignalProcessors) (DSP) 504F. The audio DSP(s) 504F may be include elementsfor compression/decompression and echo cancellation and may includeother suitable processing elements in other embodiments. Components ofthe baseband circuitry may be suitably combined in a single chip, asingle chipset, or disposed on a same circuit board in some embodiments.In some demonstrative embodiments, some or all of the constituentcomponents of the baseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 )and the application circuitry 305/405 may be implemented together suchas, for example, on a system on a chip (SOC).

In some demonstrative embodiments, the baseband circuitry 310 (FIG. 3 )and/or 410 (FIG. 4 ) may provide for communication compatible with oneor more radio technologies. For example, in some embodiments, thebaseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 ) may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), a WirelessLocal Area Network (WLAN), a Wireless Personal Area Network (WPAN).Embodiments in which the baseband circuitry 310 (FIG. 3 ) and/or 410(FIG. 4 ) is configured to support radio communications of more than onewireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 506 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 506 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 506 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 508 and provide baseband signals to the baseband circuitry 310(FIG. 3 ) and/or 410 (FIG. 4 ). RF circuitry 506 may also include atransmit signal path which may include circuitry to up-convert basebandsignals provided by the baseband circuitry 310 (FIG. 3 ) and/or 410(FIG. 4 ) and provide RF output signals to the FEM circuitry 508 fortransmission.

In some demonstrative embodiments, the receive signal path of the RFcircuitry 506 may include mixer circuitry 506 a, amplifier circuitry 506b and filter circuitry 506 c. In some demonstrative embodiments, thetransmit signal path of the RF circuitry 506 may include filtercircuitry 506 c and mixer circuitry 506 a. RF circuitry 506 may alsoinclude synthesizer circuitry 506 d for synthesizing a frequency for useby the mixer circuitry 506 a of the receive signal path and the transmitsignal path. In some demonstrative embodiments, the mixer circuitry 506a of the receive signal path may be configured to down-convert RFsignals received from the FEM circuitry 508 based on the synthesizedfrequency provided by synthesizer circuitry 506 d. The amplifiercircuitry 506 b may be configured to amplify the down-converted signalsand the filter circuitry 506 c may be a Low-Pass Filter (LPF) orBand-Pass Filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 310 (FIG. 3 )and/or 410 (FIG. 4 ) for further processing. In some demonstrativeembodiments, the output baseband signals may be zero-frequency basebandsignals, although this is not a requirement. In some demonstrativeembodiments, mixer circuitry 506 a of the receive signal path mayinclude passive mixers, although the scope of the embodiments is notlimited in this respect.

In some demonstrative embodiments, the mixer circuitry 506 a of thetransmit signal path may be configured to up-convert input basebandsignals based on the synthesized frequency provided by the synthesizercircuitry 506 d to generate RF output signals for the FEM circuitry 508.The baseband signals may be provided by the baseband circuitry 310 (FIG.3 ) and/or 410 (FIG. 4 ) and may be filtered by filter circuitry 506 c.

In some demonstrative embodiments, the mixer circuitry 506 a of thereceive signal path and the mixer circuitry 506 a of the transmit signalpath may include two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some demonstrativeembodiments, the mixer circuitry 506 a of the receive signal path andthe mixer circuitry 506 a of the transmit signal path may include two ormore mixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some demonstrative embodiments, the mixer circuitry 506 aof the receive signal path and the mixer circuitry 506 a may be arrangedfor direct downconversion and direct upconversion, respectively. In somedemonstrative embodiments, the mixer circuitry 506 a of the receivesignal path and the mixer circuitry 506 a of the transmit signal pathmay be configured for super-heterodyne operation.

In some demonstrative embodiments, the output baseband signals and theinput baseband signals may be analog baseband signals, although thescope of the embodiments is not limited in this respect. In somealternate embodiments, the output baseband signals and the inputbaseband signals may be digital baseband signals. In these alternateembodiments, the RF circuitry 506 may include Analog-To-DigitalConverter (ADC) and Digital-To-Analog Converter (DAC) circuitry and thebaseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 ) may include adigital baseband interface to communicate with the RF circuitry 506.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some demonstrative embodiments, the synthesizer circuitry 506 d maybe a fractional-N synthesizer or a fractional N/N+1 synthesizer,although the scope of the embodiments is not limited in this respect asother types of frequency synthesizers may be suitable. For example,synthesizer circuitry 506 d may be a delta-sigma synthesizer, afrequency multiplier, or a synthesizer including a phase-locked loopwith a frequency divider.

The synthesizer circuitry 506 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 506 a of the RFcircuitry 506 based on a frequency input and a divider control input. Insome demonstrative embodiments, the synthesizer circuitry 506 d may be afractional N/N+1 synthesizer.

In some demonstrative embodiments, frequency input may be provided by aVoltage Controlled Oscillator (VCO), although that is not a requirement.Divider control input may be provided by either the baseband circuitry310 (FIG. 3 ) and/or 410 (FIG. 4 ) or the applications processor 305/405depending on the desired output frequency. In some demonstrativeembodiments, a divider control input (e.g., N) may be determined from alook-up table based on a channel indicated by the applications processor305/405.

Synthesizer circuitry 506 d of the RF circuitry 506 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some demonstrative embodiments, the divider may be aDual Modulus Divider (DMD) and the phase accumulator may be a DigitalPhase Accumulator (DPA). In some demonstrative embodiments, the DMD maybe configured to divide the input signal by either N or N+1 (e.g., basedon a carry out) to provide a fractional division ratio. In some exampleembodiments, the DLL may include a set of cascaded, tunable, delayelements, a phase detector, a charge pump and a D-type flip-flop. Inthese embodiments, the delay elements may be configured to break a VCOperiod up into Nd equal packets of phase, where Nd is the number ofdelay elements in the delay line. In this way, the DLL provides negativefeedback to help ensure that the total delay through the delay line isone VCO cycle.

In some demonstrative embodiments, synthesizer circuitry 506 d may beconfigured to generate a carrier frequency as the output frequency,while in other embodiments, the output frequency may be a multiple ofthe carrier frequency (e.g., twice the carrier frequency, four times thecarrier frequency) and used in conjunction with quadrature generator anddivider circuitry to generate multiple signals at the carrier frequencywith multiple different phases with respect to each other. In somedemonstrative embodiments, the output frequency may be a LO frequency(fLO). In some demonstrative embodiments, the RF circuitry 506 mayinclude an IQ/polar converter.

FEM circuitry 508 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 511, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 506 for furtherprocessing. FEM circuitry 508 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 506 for transmission by one ormore of the one or more antennas 511. In various embodiments, theamplification through the transmit or receive signal paths may be donesolely in the RF circuitry 506, solely in the FEM 508, or in both the RFcircuitry 506 and the FEM 508.

In some demonstrative embodiments, the FEM circuitry 508 may include aTX/RX switch to switch between transmit mode and receive mode operation.The FEM circuitry may include a receive signal path and a transmitsignal path. The receive signal path of the FEM circuitry may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 506). The transmitsignal path of the FEM circuitry 508 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by RF circuitry 506), andone or more filters to generate RF signals for subsequent transmission(e.g., by one or more of the one or more antennas 511).

Processors of the application circuitry 305/405 and processors of thebaseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 ) may be used toexecute elements of one or more instances of a protocol stack. Forexample, processors of the baseband circuitry 310 (FIG. 3 ) and/or 410(FIG. 4 ), alone or in combination, may be used execute Layer 3, Layer2, or Layer 1 functionality, while processors of the baseband circuitry310 (FIG. 3 ) and/or 410 (FIG. 4 ) may utilize data (e.g., packet data)received from these layers and further execute Layer 4 functionality(e.g., transmission communication protocol (TCP) and user datagramprotocol (UDP) layers). As referred to herein, Layer 3 may include aradio resource control (RRC) layer, described in further detail below.As referred to herein, Layer 2 may include a Medium Access Control (MAC)layer, a Radio Link Control (RLC) layer, and a Packet Data ConvergenceProtocol (PDCP) layer, described in further detail below. As referred toherein, Layer 1 may include a physical (PHY) layer of a UE/RAN node,described in further detail below.

Reference is made to FIG. 6 , which schematically illustrates interfacesof a baseband circuitry 600, in accordance with some demonstrativeembodiments.

In one example, UE 102 (FIG. 1 ) and/or gNB 140 (FIG. 1 ) may includeone or more elements of baseband circuitry 600.

In some demonstrative embodiments, the baseband circuitry 600, e.g.,baseband circuitry 310 (FIG. 3 ), 410 (FIG. 4 ) and/or 500 (FIG. 5 ) mayinclude processors 504A-504E (FIG. 5 ) and a memory 504G (FIG. 5 )utilized by the processors. Each of the processors 504A-504E may includea memory interface, 604A-604E, respectively, to send/receive datato/from the memory 504G.

The baseband circuitry 310 (FIG. 3 ) and/or 410 (FIG. 4 ) may furtherinclude one or more interfaces to communicatively couple to othercircuitries/devices, such as a memory interface 612 (e.g., an interfaceto send/receive data to/from memory external to the baseband circuitry310 (FIG. 3 ) and/or 410 (FIG. 4 )), an application circuitry interface614 (e.g., an interface to send/receive data to/from the applicationcircuitry 305/405 of FIGS. 3-5 ), an RF circuitry interface 616 (e.g.,an interface to send/receive data to/from RF circuitry 506 of FIG. 5 ),a wireless hardware connectivity interface 618 (e.g., an interface tosend/receive data to/from Near Field Communication (NFC) components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components), and a power management interface620 (e.g., an interface to send/receive power or control signals to/fromthe PMIC 425.

FIG. 7 is a schematic flow-chart illustration of a method ofcommunication over common control channels, in accordance with somedemonstrative embodiments. For example, one or more of the operations ofthe method of FIG. 7 may be performed by one or more elements of asystem, e.g., system 100 (FIG. 1 ), for example, one or more UEs, e.g.,UE 102 (FIG. 1 ), a radio, e.g., radio 114 (FIG. 1 ), a receiver, e.g.,receiver 116 (FIG. 1 ), a controller, e.g., controller 124 (FIG. 1 ),and/or a message processor, e.g., message processor 128 (FIG. 1 ).

As indicated at block 702, the method may include determining a selectedCCCH message configuration from a first predefined message configurationand a second predefined message configuration, the first predefinedmessage configuration having a first predefined message bit-size, thesecond predefined message configuration having a second predefinedmessage bit-size. For example, controller 124 (FIG. 1 ) may control,cause and/or trigger UE 102 (FIG. 1 ) to determine the selected CCCHmessage configuration from the first predefined message configurationand the second predefined message configuration, the first predefinedmessage configuration having the first predefined message bit-size, andthe second predefined message configuration having the second predefinedmessage bit-size, e.g., as described above.

As indicated at block 704, the method may include generating an UL CCCHmessage according to the selected CCCH message configuration, the ULCCCH message including a MAC header including an LCID field having avalue corresponding to the selected CCCH message configuration. Forexample, controller 124 (FIG. 1 ) may control, cause and/or trigger UE102 (FIG. 1 ) to generate the UL CCCH message according to the selectedCCCH message configuration, the UL CCCH message including the MAC headerincluding the LCID field having the value corresponding to the selectedCCCH message configuration, e.g., as described above.

As indicated at block 706, the method may include transmitting the ULCCCH message to a gNB over a logical channel corresponding to theselected CCCH message configuration. For example, controller 124 (FIG. 1) may control, cause and/or trigger UE 102 (FIG. 1 ) to transmit the ULCCCH message to gNB 140 (FIG. 1 ) over the logical channel correspondingto the selected CCCH message configuration, e.g., as described above.

FIG. 8 is a schematic flow-chart illustration of a method ofcommunication over common control channels, in accordance with somedemonstrative embodiments. For example, one or more of the operations ofthe method of FIG. 8 may be performed by one or more elements of asystem, e.g., system 100 (FIG. 1 ), for example, one or more gNBs, e.g.,gNB 140 (FIG. 1 ), a radio, e.g., radio 144 (FIG. 1 ), a receiver, e.g.,receiver 146 (FIG. 1 ), a controller, e.g., controller 154 (FIG. 1 ),and/or a message processor, e.g., message processor 158 (FIG. 1 ).

As indicated at block 802, the method may include transmitting a messageincluding an indication of a selected CCCH message configuration from afirst predefined message configuration and a second predefined messageconfiguration, the first predefined message configuration having a firstpredefined message bit-size, the second predefined message configurationhaving a second predefined message bit-size. For example, controller 154(FIG. 1 ) may control, cause and/or trigger gNB 140 (FIG. 1 ) totransmit the message including the indication of the selected CCCHmessage configuration from the first predefined message configurationand the second predefined message configuration, the first predefinedmessage configuration having the first predefined message bit-size, andthe second predefined message configuration having the second predefinedmessage bit-size, e.g., as described above.

As indicated at block 804, the method may include receiving an UL CCCHmessage from a UE over a logical channel corresponding to the selectedCCCH message configuration, the UL CCCH message including a MAC headerincluding an LCID field having a value corresponding to the selectedCCCH message configuration. For example, controller 154 (FIG. 1 ) maycontrol, cause and/or trigger gNB 140 (FIG. 1 ) and/or radio 144 (FIG. 1) to receive the UL CCCH message from UE 102 (FIG. 1 ) over the logicalchannel corresponding to the selected CCCH message configuration, the ULCCCH message including the MAC header including the LCID field havingthe value corresponding to the selected CCCH message configuration,e.g., as described above.

Reference is made to FIG. 9 , which schematically illustrates a productof manufacture 900, in accordance with some demonstrative embodiments.Product 900 may include one or more tangible computer-readable(“machine-readable”) non-transitory storage media 902, which may includecomputer-executable instructions, e.g., implemented by logic 904,operable to, when executed by at least one computer processor, enablethe at least one computer processor to implement one or more operationsat UE 102 (FIG. 1 ), gNB 140 (FIG. 1 ), radio 114 (FIG. 1 ), radio 144(FIG. 1 ), controller 124 (FIG. 1 ), controller 154 (FIG. 1 ), receiver116 (FIG. 1 ), transmitter 118 (FIG. 1 ), message processor 128 (FIG. 1), receiver 146 (FIG. 1 ), transmitter 158 (FIG. 1 ), and/or messageprocessor 158 (FIG. 1 ), to cause UE 102 (FIG. 1 ), gNB 140 (FIG. 1 ),radio 114 (FIG. 1 ), radio 144 (FIG. 1 ), controller 124 (FIG. 1 ),controller 154 (FIG. 1 ), receiver 116 (FIG. 1 ), transmitter 118 (FIG.1 ), message processor 128 (FIG. 1 ), receiver 146 (FIG. 1 ),transmitter 158 (FIG. 1 ), and/or message processor 158 (FIG. 1 ) toperform, trigger and/or implement one or more operations and/orfunctionalities, and/or to perform, trigger and/or implement one or moreoperations and/or functionalities described with reference to the FIGS.1, 2, 3, 4, 5, 6, 7 and/or 8 , and/or one or more operations describedherein. The phrases “non-transitory machine-readable medium” and“computer-readable non-transitory storage media” may be directed toinclude all computer-readable media, with the sole exception being atransitory propagating signal.

In some demonstrative embodiments, product 900 and/or machine-readablestorage media 902 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage media 902 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 904 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 904 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising logic and circuitryconfigured to cause a User Equipment (UE) to determine a selected CommonControl Channel (CCCH) message configuration from a first predefinedmessage configuration and a second predefined message configuration, thefirst predefined message configuration having a first predefined messagebit-size, the second predefined message configuration having a secondpredefined message bit-size; generate an Uplink (UL) CCCH messageaccording to the selected CCCH message configuration, the UL CCCHmessage comprising a Medium Access Control (MAC) header comprising aLogical Channel Identify (ID) (LCID) field having a value correspondingto the selected CCCH message configuration; and transmit the UL CCCHmessage to a Next Generation Node B (gNB) over a logical channelcorresponding to the selected CCCH message configuration.

Example 2 includes the subject matter of Example 1, and optionally,wherein the apparatus is configured to cause the UE to transmit the ULCCCH message over a first logical channel (CCCH channel), when theselected CCCH message configuration comprises the first predefinedmessage configuration, and to transmit the UL CCCH message over a secondlogical channel (CCCH1 channel), when the selected CCCH messageconfiguration comprises the second predefined message configuration.

Example 3 includes the subject matter of Example 1 or 2, and optionally,wherein the first predefined message configuration comprises a firstidentifier field having a first predefined bit-size, and the secondpredefined message configuration comprises a second identifier fieldhaving a second predefined bit-size different from the first predefinedbit-size

Example 4 includes the subject matter of any one of Examples 1-3, andoptionally, wherein the apparatus is configured to cause the UE to setthe LCID field to a first predefined LCID value when the selected CCCHmessage configuration comprises the first predefined messageconfiguration, and to set the LCID field to a second predefined LCIDvalue, different from the first predefined LCID value, when the selectedCCCH message configuration comprises the second predefined messageconfiguration.

Example 5 includes the subject matter of any one of Examples 1-4, andoptionally, wherein the apparatus is configured to cause the UE todetermine the selected CCCH message configuration based on an indicationin a message from the gNB.

Example 6 includes the subject matter of any one of Examples 1-5, andoptionally, wherein the apparatus is configured to cause the UE todetermine the selected CCCH message configuration based on an indicationin a broadcast message from the gNB.

Example 7 includes the subject matter of any one of Examples 1-6, andoptionally, wherein the first predefined message configurationcorresponds to a first CCCH message type, and the second predefinedmessage configuration corresponds to a second CCCH message typedifferent from the first CCCH message type.

Example 8 includes the subject matter of any one of Examples 1-7, andoptionally, wherein the UL CCCH message comprises a Radio ResourceControl (RRC) message.

Example 9 includes the subject matter of any one of Examples 1-8, andoptionally, wherein the UL CCCH message comprises a Radio ResourceControl (RRC) Resume Request message.

Example 10 includes the subject matter of any one of Examples 1-9, andoptionally, wherein the first predefined message configuration comprisesa first Radio Resource Control (RRC) Resume Request (RRCResumeRequest)message configuration, and the second predefined message configurationcomprises a second RRC Resume Request (RRCResumeRequest1) messageconfiguration.

Example 11 includes the subject matter of Example 10, and optionally,wherein the first RRC Resume Request message configuration comprises afirst resume identity (ResumeIdentity) field having a first predefinedResumeIdentity bit-size, and the second RRC Resume Request messageconfiguration comprises a second resume identity field having a secondpredefined ResumeIdentity bit-size shorter than the first predefinedResumeIdentity bit-size.

Example 12 includes the subject matter of Example 10 or 11, andoptionally, wherein the second RRC Resume Request message configurationcomprises a 40-bit resume identity (ResumeIdentity) field configured fora 40-bit Radio Network Temporary Identity (RNTI) value, and the firstRRC Resume Request message configuration comprises a 16-bit resumeidentity field configured for a 16-bit truncated RNTI value.

Example 13 includes the subject matter of any one of Examples 9-12, andoptionally, wherein the RRC Resume Request message comprises a 16-bitresume Message Authentication Code for Integrity (resumeMAC-I) field,and a Resume Cause (ResumeCause) field.

Example 14 includes the subject matter of any one of Examples 1-8, andoptionally, wherein the UL CCCH message comprises a Radio ResourceControl (RRC) Setup Request, an RRC Reestablishment Request, or an RRCSystem Information (Info) Request.

Example 15 includes the subject matter of any one of Examples 1-14, andoptionally, wherein the first predefined message bit-size comprises a48-bit size, and the second predefined message bit-size comprises a64-bit size.

Example 16 includes the subject matter of any one of Examples 1-15, andoptionally, comprising a radio to transmit the UL CCCH message.

Example 17 includes the subject matter of Example 16, and optionally,comprising one or more antennas connected to the radio, a memory, and aprocessor.

Example 18 includes an apparatus comprising logic and circuitryconfigured to cause a Next Generation Node B (gNB) to transmit a messagecomprising an indication of a selected Common Control Channel (CCCH)message configuration from a first predefined message configuration anda second predefined message configuration, the first predefined messageconfiguration having a first predefined message bit-size, the secondpredefined message configuration having a second predefined messagebit-size; and receive an Uplink (UL) CCCH message from a User Equipment(UE) over a logical channel corresponding to the selected CCCH messageconfiguration, the UL CCCH message comprising a Medium Access Control(MAC) header comprising a Logical Channel Identify (ID) (LCID) fieldhaving a value corresponding to the selected CCCH message configuration.

Example 19 includes the subject matter of Example 18, and optionally,wherein the apparatus is configured to cause the gNB to receive the ULCCCH message over a first logical channel (CCCH channel), when theselected CCCH message configuration comprises the first predefinedmessage configuration, and to receive the UL CCCH message over a secondlogical channel (CCCH1 channel), when the selected CCCH messageconfiguration comprises the second predefined message configuration.

Example 20 includes the subject matter of Example 18 or 19, andoptionally, wherein the first predefined message configuration comprisesa first identifier field having a first predefined bit-size, and thesecond predefined message configuration comprises a second identifierfield having a second predefined bit-size different from the firstpredefined bit-size.

Example 21 includes the subject matter of any one of Examples 18-20, andoptionally, wherein the LCID field comprises a first predefined LCIDvalue when the selected CCCH message configuration comprises the firstpredefined message configuration, and wherein the LCID field comprises asecond predefined LCID value, different from the first predefined LCIDvalue, when the selected CCCH message configuration comprises the secondpredefined message configuration.

Example 22 includes the subject matter of any one of Examples 18-21, andoptionally, wherein the first predefined message configurationcorresponds to a first CCCH message type, and the second predefinedmessage configuration corresponds to a second CCCH message typedifferent from the first CCCH message type.

Example 23 includes the subject matter of any one of Examples 18-22, andoptionally, wherein the UL CCCH message comprises a Radio ResourceControl (RRC) message.

Example 24 includes the subject matter of any one of Examples 18-23, andoptionally, wherein the UL CCCH message comprises a Radio ResourceControl (RRC) Resume Request message.

Example 25 includes the subject matter of any one of Examples 18-24, andoptionally, wherein the first predefined message configuration comprisesa first Radio Resource Control (RRC) Resume Request (RRCResumeRequest)message configuration, and the second predefined message configurationcomprises a second RRC Resume Request (RRCResumeRequest1) messageconfiguration.

Example 26 includes the subject matter of Example 25, and optionally,wherein the first RRC Resume Request message configuration comprises afirst resume identity (ResumeIdentity) field having a first predefinedResumeIdentity bit-size, and the second RRC Resume Request messageconfiguration comprises a second resume identity field having a secondpredefined ResumeIdentity bit-size shorter than the first predefinedResumeIdentity bit-size.

Example 27 includes the subject matter of Example 25 or 26, andoptionally, wherein the second RRC Resume Request message configurationcomprises a 40-bit resume identity (ResumeIdentity) field configured fora 40-bit Radio Network Temporary Identity (RNTI) value, and the firstRRC Resume Request message configuration comprises a 16-bit resumeidentity field configured for a 16-bit truncated RNTI value.

Example 28 includes the subject matter of any one of Examples 24-27, andoptionally, wherein the RRC Resume Request message comprises a 16-bitresume Message Authentication Code for Integrity (resumeMAC-I) field,and a Resume Cause (ResumeCause) field.

Example 29 includes the subject matter of any one of Examples 18-23, andoptionally, wherein the UL CCCH message comprises a Radio ResourceControl (RRC) Setup Request, an RRC Reestablishment Request, or an RRCSystem Information (Info) Request.

Example 30 includes the subject matter of any one of Examples 18-29, andoptionally, wherein the first predefined message bit-size comprises a48-bit size, and the second predefined message bit-size comprises a64-bit size.

Example 31 includes the subject matter of any one of Examples 18-30, andoptionally, wherein the apparatus is configured to cause the gNB tobroadcast the message.

Example 32 includes the subject matter of any one of Examples 18-31, andoptionally, comprising a radio to transmit the message and to receivethe CCCH message.

Example 33 includes the subject matter of Example 32, and optionally,comprising one or more antennas connected to the radio, a memory, and aprocessor.

Example 34 comprises an apparatus comprising means for executing any ofthe described operations of Examples 1-33.

Example 35 comprises a machine readable medium that stores instructionsfor execution by a processor to perform any of the described operationsof Examples 1-33.

Example 36 comprises an apparatus comprising: a memory interface; andprocessing circuitry configured to: perform any of the describedoperations of Examples 1-33.

Example 37 comprises a method to perform any of the described operationsof Examples 1-33.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manymodifications, substitutions, changes, and equivalents may occur tothose skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and changesas fall within the true spirit of the disclosure.

What is claimed is:
 1. An apparatus comprising logic and circuitryconfigured to cause a User Equipment (UE) to: determine a Common ControlChannel (CCCH) message configuration selected from a first predefinedmessage configuration that includes a first Radio Resource Control (RRC)message configuration, and a second predefined message configurationthat includes a second RRC message configuration, the first predefinedmessage configuration having a first predefined message bit-size, thesecond predefined message configuration having a second predefinedmessage bit-size; generate an Uplink (UL) CCCH message according to theselected CCCH message configuration, the UL CCCH message comprising aRRC message having an RRC System Information (Info) Request, and aMedium Access Control (MAC) header comprising a Logical Channel Identify(ID) (LCID) field having a value corresponding to the selected CCCHmessage configuration; and transmit the UL CCCH message to a basestation over a logical channel corresponding to the selected CCCHmessage configuration.
 2. The apparatus of claim 1, wherein the logicand circuitry are configured to cause the UE to transmit the UL CCCHmessage over a first logical channel (CCCH channel), when the selectedCCCH message configuration comprises the first predefined messageconfiguration, and to transmit the UL CCCH message over a second logicalchannel (CCCH1 channel), when the selected CCCH message configurationcomprises the second predefined message configuration.
 3. The apparatusof claim 1, wherein the first predefined message configuration comprisesa first identifier field having a first predefined bit-size, and thesecond predefined message configuration comprises a second identifierfield having a second predefined bit-size different from the firstpredefined bit-size.
 4. The apparatus of claim 1, wherein the logic andcircuitry are configured to cause the UE to set the LCID field to afirst predefined LCID value when the selected CCCH message configurationcomprises the first predefined message configuration, and to set theLCID field to a second predefined LCID value, different from the firstpredefined LCID value, when the selected CCCH message configurationcomprises the second predefined message configuration.
 5. The apparatusof claim 1, wherein the logic and circuitry are configured to cause theUE to determine the selected CCCH message configuration based on anindication in a message from the base station.
 6. The apparatus of claim1, wherein the first predefined message configuration corresponds to afirst CCCH message type, and the second predefined message configurationcorresponds to a second CCCH message type different from the first CCCHmessage type.
 7. The apparatus of claim 1, wherein the first predefinedmessage configuration comprises a first Radio Resource Control (RRC)Resume Request (RRCResumeRequest) message configuration, and the secondpredefined message configuration comprises a second RRC Resume Request(RRCResumeRequest1) message configuration.
 8. The apparatus of claim 7,wherein the first RRC Resume Request message configuration comprises afirst resume identity (ResumeIdentity) field having a first predefinedResumeIdentity bit-size, and the second RRC Resume Request messageconfiguration comprises a second resume identity field having a secondpredefined ResumeIdentity bit-size shorter than the first predefinedResumeIdentity bit-size.
 9. The apparatus of claim 1, wherein the ULCCCH message further comprises a Radio Resource Control (RRC) SetupRequest, or an RRC Reestablishment Request.
 10. The apparatus of claim 1comprising a radio to transmit the UL CCCH message.
 11. The apparatus ofclaim 10 comprising one or more antennas connected to the radio, amemory, and a processor.
 12. An apparatus comprising logic and circuitryconfigured to cause a base station to: transmit a message comprising anindication of a Common Control Channel (CCCH) message configurationselected from a first predefined message configuration that includes afirst Radio Resource Control (RRC) message configuration, and a secondpredefined message configuration that includes a second RRC messageconfiguration, the first predefined message configuration having a firstpredefined message bit-size, the second predefined message configurationhaving a second predefined message bit-size; and receive an Uplink (UL)CCCH message from a User Equipment (UE) over a logical channelcorresponding to the selected CCCH message configuration, the UL CCCHmessage comprising a RRC message having an RRC System Information (Info)Request, and a Medium Access Control (MAC) header comprising a LogicalChannel Identify (ID) (LCID) field having a value corresponding to theselected CCCH message configuration.
 13. The apparatus of claim 12,wherein the logic and circuitry are configured to cause the base stationto receive the UL CCCH message over a first logical channel (CCCHchannel), when the selected CCCH message configuration comprises thefirst predefined message configuration, and to receive the UL CCCHmessage over a second logical channel (CCCH1 channel), when the selectedCCCH message configuration comprises the second predefined messageconfiguration.
 14. The apparatus of claim 12, wherein the firstpredefined message configuration comprises a first identifier fieldhaving a first predefined bit-size, and the second predefined messageconfiguration comprises a second identifier field having a secondpredefined bit-size different from the first predefined bit-size. 15.The apparatus of claim 12, wherein the LCID field comprises a firstpredefined LCID value when the selected CCCH message configurationcomprises the first predefined message configuration, and wherein theLCID field comprises a second predefined LCID value, different from thefirst predefined LCID value, when the selected CCCH messageconfiguration comprises the second predefined message configuration. 16.The apparatus of claim 12, wherein the first predefined messageconfiguration corresponds to a first CCCH message type, and the secondpredefined message configuration corresponds to a second CCCH messagetype different from the first CCCH message type.
 17. The apparatus ofclaim 12, wherein the first predefined message configuration comprises afirst Radio Resource Control (RRC) Resume Request (RRCResumeRequest)message configuration, and the second predefined message configurationcomprises a second RRC Resume Request (RRCResumeRequest1) messageconfiguration.
 18. The apparatus of claim 17, wherein the first RRCResume Request message configuration comprises a first resume identity(ResumeIdentity) field having a first predefined ResumeIdentitybit-size, and the second RRC Resume Request message configurationcomprises a second resume identity field having a second predefinedResumeIdentity bit-size shorter than the first predefined ResumeIdentitybit-size.
 19. The apparatus of claim 12 comprising a radio to transmitthe message and to receive the UL CCCH message.
 20. A product comprisingone or more tangible computer-readable non-transitory storage mediacomprising computer-executable instructions operable to, when executedby at least one processor, enable the at least one processor to cause aUser Equipment (UE) to: determine a Common Control Channel (CCCH)message configuration selected from a first predefined messageconfiguration that includes a first Radio Resource Control (RRC) messageconfiguration, and a second predefined message configuration thatincludes a second RRC message configuration, the first predefinedmessage configuration having a first predefined message bit-size, thesecond predefined message configuration having a second predefinedmessage bit-size; generate an Uplink (UL) CCCH message according to theselected CCCH message configuration, the UL CCCH message comprising aRRC message having an RRC System Information (Info) Request, and aMedium Access Control (MAC) header comprising a Logical Channel Identify(ID) (LCID) field having a value corresponding to the selected CCCHmessage configuration; and transmit the UL CCCH message to a basestation over a logical channel corresponding to the selected CCCHmessage configuration.
 21. The product of claim 20, wherein theinstructions, when executed, cause the UE to transmit the UL CCCHmessage over a first logical channel (CCCH channel), when the selectedCCCH message configuration comprises the first predefined messageconfiguration, and to transmit the UL CCCH message over a second logicalchannel (CCCH1 channel), when the selected CCCH message configurationcomprises the second predefined message configuration.
 22. The productof claim 20, wherein the instructions, when executed, cause the UE toset the LCID field to a first predefined LCID value when the selectedCCCH message configuration comprises the first predefined messageconfiguration, and to set the LCID field to a second predefined LCIDvalue, different from the first predefined LCID value, when the selectedCCCH message configuration comprises the second predefined messageconfiguration.
 23. A product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone processor, enable the at least one processor to cause a base stationto: transmit a message comprising an indication of a Common ControlChannel (CCCH) message configuration selected from a first predefinedmessage configuration that includes a first Radio Resource Control (RRC)message configuration, and a second predefined message configurationthat includes a second RRC message configuration, the first predefinedmessage configuration having a first predefined message bit-size, thesecond predefined message configuration having a second predefinedmessage bit-size; and receive an Uplink (UL) CCCH message from a UserEquipment (UE) over a logical channel corresponding to the selected CCCHmessage configuration, the UL CCCH message comprising a RRC messagehaving an RRC System Information (Info) Request, and a Medium AccessControl (MAC) header comprising a Logical Channel Identify (ID) (LCID)field having a value corresponding to the selected CCCH messageconfiguration.
 24. The product of claim 23, wherein the instructions,when executed, cause the base station to receive the UL CCCH messageover a first logical channel (CCCH channel), when the selected CCCHmessage configuration comprises the first predefined messageconfiguration, and to receive the UL CCCH message over a second logicalchannel (CCCH1 channel), when the selected CCCH message configurationcomprises the second predefined message configuration.
 25. The productof claim 24, wherein the LCID field comprises a first predefined LCIDvalue when the selected CCCH message configuration comprises the firstpredefined message configuration, and wherein the LCID field comprises asecond predefined LCID value, different from the first predefined LCIDvalue, when the selected CCCH message configuration comprises the secondpredefined message configuration.